Sume SDK subscribeFormatRun: 20-minute timeout vs 90-minute runs

subscribeFormatRun in @sume-com/sdk polls every 2 seconds and times out at 20 minutes by default, while a Format run can live 90. Set the timeout on purpose.

5 min readSume
All posts

subscribeFormatRun in @sume-com/sdk polls the run, defaults to a 20 minute timeout and a 2 second interval, and resolves for any terminal status, so a failed run still resolves and you must read the status yourself. It throws SumeRunRequestError on a request problem and SumeRunTimeoutError when the clock runs out. A Format run can live up to 90 minutes, so the default can give up on a run that is still healthy.

A timeout of the helper does not stop the run or the spend. Keep the receipt id and keep polling, or switch to the webhook.

Helpers and defaults

SDK wait helpers per Sume docs (read 2026-10-03)
HelperDefault timeoutNotes
subscribeFormatRun20 minutes2 second poll; resolves on any terminal status
waitForRun10 minutesFamily argument is required
waitForJobSee SDK docsFor job ids

Client setup

createSumeClient sends the key as x-api-key. Sending both an Authorization and x-api-key header returns 401. The client retries 408, 429 and 5xx twice, and retries a POST only when an Idempotency-Key is present, which is one more reason to set idempotency_key on every run.

Sources

Related posts

More in Formats

All Formats posts

Written by Sume