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.

4 min readSume
All posts

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.

Waiting on a 600-second job, arithmetic from the documented slices, read 2026-10-01.
SliceCalls 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

All Integrations posts

Written by Sume