Sume image_not_fetchable: make the input a public HTTPS image URL
image_not_fetchable and input_media_unreachable mean Sume could not fetch or mirror your media safely. Use a public HTTPS URL and retry.
image_not_fetchable and input_media_unreachable mean Sume could not fetch or mirror the input media safely. Make sure the input is a public HTTPS image URL, then retry (read 2026-10-06 in the errors docs).
What usually causes it?
A URL behind a login, a private network address, an expired signed link, or plain HTTP.
What should I do in practice?
Storage configuration errors are reported in the same group.
- Open the URL in a logged-out browser.
- Use a link that outlives the job.
- Contact support with the request id if it persists.
Sources
Related posts
More in Developers
- Sume job error categories and the next action for each
Failed Sume jobs carry a category: validation, auth, quota, queue, generation_unavailable, generation_rejected, timeouts, runtime_unavailable or internal.
- Sume job.canceled and job.failed webhooks both say status ERROR
A Sume job.failed and a job.canceled webhook both carry status ERROR and an error object. Branch on the event name, not on status, to tell them apart.
- Sume job status logs_available is false: read events_url instead
A Sume job status carries logs_available, false while diagnostics live behind events_url. Read the events timeline for the lifecycle, not inline logs.
- Sume job statuses: queued, processing, completed, failed, canceled
The five Sume job statuses and what a client should do at each. Resources use a different set: processing, ready, failed, canceled and archived.
Written by Sume