Make webhook logs last 3 days: keep Sume job ids and events yourself

Make keeps webhook logs for 3 days on standard plans and 30 days on Enterprise (Make webhooks, read 2026-10-02). A Sume video can be requested on Monday and questioned the next week, so write the Sume job_id to a table of your own and use Sume's job events as the audit trail.

Two Make settings that affect what you can look up

If you turn on the confidentiality setting, Make will show that a run happened but not what Sume sent. That is useful for privacy and unhelpful for debugging.

What Sume already records

Each Sume job keeps a public event timeline at GET /v1/jobs/{job_id}/events: created, queued, started, completed or failed, and webhook.delivery. Public events do not expose raw provider task ids or URLs. The event list is a pull snapshot, not a stream, so read it when you need it.

The job's webhook_delivery state on the receipt tells you whether delivery succeeded, and a Redeliver call re-sends the terminal event if the Make side lost it.

A minimal ledger

• At submit, save the job_id, the scenario run, and the request time in a Data Store or your own database.
• In the webhook scenario, update that row with the terminal status and result URL.
• Treat Make's log as short-lived debugging help, not as the record.

Honest limit

Sume does not hold your Make execution history, and Make does not hold the Sume job. Only the shared id links them. If you did not save the id, you can still list jobs with GET /v1/jobs, which returns the jobs your API key's member created, but matching them back to scenario runs by time is guesswork.