Sonnet 5.5 and a 10-minute render: about 12 jobs_wait calls
A Sume job that takes ten minutes needs roughly 11 to 12 jobs_wait calls at the 55 and 50 second slices. How to keep a Sonnet 5.5 tool loop that short.

A job that takes ten minutes needs about 12 jobs_wait calls at the default 50-second slice, or about 11 at the 55-second cap, since 600 divided by 50 is 12 and by 55 is just under 11. Each call is a model turn, so a Claude Sonnet 5.5 loop pays for every one.
The slice lengths are from Sume's MCP docs. Sonnet 5.5's id and pricing are from Anthropic's models overview, read 2026-10-01. I have not measured token counts, so none are given.
What are the numbers?
Anthropic lists Sonnet 5.5 as claude-sonnet-5-5 at $2 per million input and $10 per million output tokens. Sume documents jobs_wait as default 50 seconds, cap 55.
| Slice | Calls for 600 s |
|---|---|
| 50 s (default) | 12 |
| 55 s (cap) | 11 |
What does one expired slice mean?
wait_slice_expired means the slice ended before the job did. Call jobs_wait again with the same ids. It is not a failure and not a reason to resubmit, and a 524 is a transport failure, never a job outcome, per the jobs page.
How do I keep the loop cheap?
Set wait_ms toward the cap, wait on all ids in one call (up to 20), and tell the model in the system prompt to call nothing else between slices. For a long unattended render, a webhook to a public HTTPS URL removes the polling turns entirely.
Sources
Related posts
More in Integrations
- Code by Zapier 225 requests per 10 seconds and Sume 429s
Zapier lists 225 requests per 10 seconds for Code by Zapier on Pro and Team. Sume has its own 429 rate_limited: honor retry-after and send an Idempotency-Key.
- Code by Zapier 10-minute runtime vs Sume's 30-second sync wait
Code by Zapier can run 10 minutes on action steps, but Sume's sync wait caps at 30 seconds. Submit async, keep the job id, and poll instead of holding the step.
- Codex network policy now follows redirects: allow Sume's hosts
Codex 0.157.0 enforces network restrictions across redirects and cancels traffic when a policy change revokes access. Which Sume hosts to allow.
- Codex 0.158 approval review retry: what it means for a Sume call
Codex 0.158.0 retries an approval review when new user input arrives instead of aborting the pending action. Keep the Sume call's idempotency_key stable.
Written by Sume