Retool resource block 10-minute limit and Sume async jobs

Do not hold a Retool resource block open for the whole Sume render. Submit with mode: "async" (the default) or mode: "webhook", which returns a 202 with the job id at once, and let a later step or a webhook-triggered workflow handle the result. The block then finishes in seconds, well inside Retool's 10-minute limit.

What are the Retool limits?

Retool's limits page, read 2026-10-01, gives these figures for workflows.

Why not use sync mode?

Sume's sync mode waits up to wait_timeout_seconds, capped at 30, and then returns the same envelope. If the job is not terminal you poll; you do not resubmit. Because a 2xx means paid work is in flight, a second submit would pay twice. See Jobs and results.

How do I finish the job inside Retool?

Two shapes work. In webhook mode, send webhook_url with the submit; Sume posts a terminal event and a second workflow with a webhook trigger handles it, as in a Retool webhook relay. In async mode, poll status_url until terminal is true, then GET result_url once result_ready is true, with a wait between polls instead of a tight loop.

Even with a webhook, keep status_url polling available as a backup for deliveries that never arrive.

What do I store between steps?

The job_id from the first response. If a block times out locally, recover with that id through the jobs API rather than submitting duplicate paid work.