n8n Wait node under 65 seconds: how to poll a Sume job
n8n keeps waits under 65 seconds in memory and saves longer ones to the database. Poll a Sume job with next_poll_after_seconds, or switch to a webhook resume.
Poll status_url in a loop, wait next_poll_after_seconds between checks, and know which side of 65 seconds the wait lands on. The n8n page says waits under 65 seconds do not offload execution data to the database, and longer waits do.
Sume behavior is from the Jobs and results docs; the n8n text was read 2026-09-30.
What changes at 65 seconds?
n8n states: “For wait times less than 65 seconds, the workflow doesn't offload execution data to the database.” Longer waits persist it. Its resume modes include After Time Interval and On Webhook Call.
| Approach | n8n behavior | Sume side |
|---|---|---|
| Wait under 65 s | Not offloaded to the database | Poll status_url again |
| Wait over 65 s | Saved to the database | Poll status_url again |
| Resume on webhook call | A resume mode n8n lists | Signed job.completed |
Where does the wait length come from?
The async 202 and status responses can carry next_poll_after_seconds. Feed it to the Wait node instead of a fixed number, and fall back to your own interval when the field is absent. Stop the loop on a terminal status: completed, failed or canceled.
curl https://api.sume.com/v1/jobs/job_123/status \
-H "Authorization: Bearer $SUME_API_KEY"When is a webhook resume the better fit?
For jobs that run long, the On Webhook Call mode means no polling at all: submit with a public HTTPS webhook_url and let the signed job.completed, job.failed or job.canceled event resume the run. Verify the signature before you trust the body.
Does a failed poll mean the job failed?
No. A timeout or error on the polling request says nothing about the job, which keeps running. Poll again and never resubmit the paid request.
Sources
Related posts
More in Developers
- Next.js image SSRF fix: narrow remotePatterns for Sume
Next.js patched an Image Optimization SSRF via allow-listed remote URLs. Allow only media.sume.com for Sume images, and never raw provider hosts.
- 429 backoff with jitter in Python: OpenAI's advice, Sume's headers
OpenAI recommends exponential backoff with random jitter on 429. A Python status poller that honors Sume's retry-after first and falls back to backoff.
- OpenAI 429 slow_down vs 503 server_is_overloaded, and Sume
OpenAI now splits 429 slow_down (traffic ramping too fast) from 503 server_is_overloaded. Here is how each maps to Sume's 429 scope and 503 retry rules.
- OpenAI Agents SDK imageGenerationTool action edit and Sume
imageGenerationTool() takes action: 'generate' | 'edit' | 'auto' in openai-agents-js 0.18.0. To edit with Sume instead, wrap its image route as a function tool.
Written by Sume