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.

4 min readSume
All posts

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.

Public job events (read 2026-10-06)
EventTells you
job.createdSume stored the job
job.queuedIt waits to run
job.startedA worker picked it up
generation.submittedGeneration work began
job.completed, job.failed, job.canceledTerminal outcome
webhook.deliveryA 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

All Developers posts

Written by Sume