Make free plan 5-minute execution cap vs Core 40 minutes for Sume jobs

The limit

On Make's pricing page, the Free plan lists a 5-minute maximum execution time and Core lists 40 minutes. A Sume video job can take longer than a Free run allows, so a scenario that submits a job and sleeps until it finishes will be cut off while the job keeps running and billing.

The fix is structural: one scenario submits, a second one receives the result. Neither needs to wait.

Make plan limits

From the pricing page.

Two scenarios

Scenario A: an HTTP module POSTs the generation request with mode: "webhook", a public HTTPS webhook_url and an Idempotency-Key, then stops. Scenario B starts from a custom webhook, checks the signature, and acts on job.completed, job.failed or job.canceled.

Sume's own sync mode waits at most 30 seconds, so it is for quick jobs only. Webhook delivery tries up to 10 times, 30 seconds apart, so scenario B can be briefly off without losing the event. Keep a poll of /v1/jobs/:id/status as a backup, using the next_poll_after_seconds hint.

curl -X POST https://api.sume.com/v1/image-1.0/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Idempotency-Key: scn-a-row-1042" \
  -H "Content-Type: application/json" \
  -d '{"prompt":"Studio shot of a steel water bottle","mode":"webhook","webhook_url":"https://hook.example.com/sume"}'

Caveats

See communication modes for the exact behavior.

• The Free plan allows 2 active scenarios, so the two-scenario split uses both of them.
• Rows I could not read on the page are marked not read: check them before you buy.
• Never retry a paid create with a new key; Make's error handlers must reuse the original.