Make webhook logs kept 3 days: recover a Sume result later

Once Make's webhook log is gone, the Sume job is not. Make's help page says it stores webhook logs for 3 days, or 30 days on Enterprise. A Sume job keeps its own record, so the way back is the stored job_id: read the job and its events, and if the callback never landed, call redeliver.

Make's retention is from its Webhooks help page; the Sume side is from Jobs and results and Webhooks, read 2026-10-01.

What should I store when the scenario submits?

Sume's docs say to store the job id from submit responses so your integration can recover work after process restarts. In Make, write it to a data store or a sheet row next to the request, not only to the scenario's execution history.

Where do I see what happened to the callback?

Job events are a public timeline for debugging and recovery, and they include webhook.delivery. The delivery status vocabulary is pending, delivering, delivered, retrying, failed, exhausted; the attempt count is visible on the job object and in job events when available.

How do I get the callback again?

Redeliver re-POSTs the job's real terminal event (job.completed, job.failed or job.canceled) with a fresh timestamp and signature, and the docs say this still works after automatic attempts are exhausted. It needs the jobs:write scope and does not change the destination URL.

Do not use Send test for this: it posts a dummy webhook.test payload and never replays a real job.

curl -X POST https://api.sume.com/v1/jobs/job_123/webhook/redeliver \
  -H "Authorization: Bearer $SUME_API_KEY"

Will redelivery run my scenario twice?

It can, if the first delivery did arrive. Treat job_id as the idempotency key on the Make side. For more on failed deliveries see debug failed webhook deliveries.