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.
If a Sume job's status shows logs_available: false, there are no inline logs to read, and the lifecycle diagnostics are exposed through events_url. Fetch GET /v1/jobs/:id/events for the public timeline instead. It is a pull snapshot, not a stream: Sume has no SSE or WebSocket transport on the Developer API today.
What the events show
The Jobs docs list the public events. They do not show raw provider task ids or raw provider URLs.
| Event | Tells you |
|---|---|
job.created | Sume stored the job |
job.queued | It waits to run |
job.started | A worker picked it up |
generation.submitted | Generation work began |
job.completed, job.failed, job.canceled | Terminal outcome |
webhook.delivery | A callback attempt |
Read the timeline
curl https://api.sume.com/v1/jobs/job_123/events \
-H "Authorization: Bearer $SUME_API_KEY"Using it when migrating a pipeline
A pipeline that tailed vendor logs can log the event names and times instead. Keep the request id for support, and leave signed URLs and keys out of your logs.
Sources
Related posts
More in Developers
- 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.
- Sume job webhook events: job.completed, job.failed, job.canceled
Sume sends only terminal job events: job.completed, job.failed and job.canceled. No progress events. Failed and canceled payloads carry status ERROR.
- Sume job webhook: request_id equals job_id, store one
In a Sume job webhook payload, request_id and job_id are the same value. Which to use as your dedupe key, and what else the payload carries.
- Sume jobs list: no next_cursor on the last page ends the loop
GET /v1/jobs returns up to 100 jobs newest first. Pass data.next_cursor back as starting_after, and stop when it is absent. Do not build a cursor yourself.
Written by Sume