Pipedream 30-second timeout: call Sume in async mode, not sync
Pipedream HTTP workflows time out at 30 seconds by default. Sume sync waits up to 30 seconds too, so submit async and take the result by webhook or poll.
Use mode: "async": Pipedream's page gives HTTP-triggered workflows a 30-second default limit per execution, and a Sume sync request may itself wait up to 30 seconds, leaving no room for the rest of the workflow. Async returns 202 at once with a job id to poll or receive by webhook.
Sume behavior is from the Jobs and results docs; the Pipedream text was read 2026-09-30.
What are the Pipedream limits?
The default is 30 seconds per execution for HTTP-triggered workflows, which Pipedream says can be raised to 300 seconds on the free plan or 750 seconds on paid plans.
| Where | Value | Note |
|---|---|---|
| Pipedream HTTP workflow, default | 30 seconds | Raisable, per Pipedream |
| Pipedream, raised | 300 or 750 seconds | Free or paid, per Pipedream |
Sume sync wait | wait_timeout_seconds, max 30 | Bounds one request, not the job |
| Sume async | 202 at once | Poll or webhook after |
What happens if sync times out?
The job keeps running. The response reports sync.timed_out, or sync.capacity_exhausted when the bounded wait cannot be held, and you continue from the job id. Do not resubmit; a client-side timeout does not cancel the job and it still bills.
What does the async call look like?
Send an Idempotency-Key so a workflow retry returns the original job, and read status_url from the 202 body.
curl -X POST https://api.sume.com/v1/image-1.0/generate \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: pipedream-demo-001" \
-d '{"prompt":"Studio photo of a ceramic mug","mode":"async"}'How does the workflow get the result?
Either a separate HTTP-triggered workflow receives the signed job.completed webhook, or a second workflow that runs on your schedule polls status_url and waits next_poll_after_seconds when it is present.
Sources
Related posts
More in Developers
- Pipedream 512KB body limit and Sume run webhook payloads
Pipedream limits HTTP trigger bodies to 512KB by default. Sume run webhooks can carry up to 1 MiB, so plan for a slim relay or the result_url fetch.
- Prompt expansion switch for Wan 3.0 and MiniMax H3 Max on Sume
Krea's H3 Max Turbo has prompt expansion modes. Sume's video model_params allowlist is empty in v1, so Wan 3.0 and H3 Max have no such switch.
- Python Workers ASGI: a FastAPI Sume webhook receiver
Python Workers now accept ASGI frameworks. A FastAPI Sume receiver keeps the same rules there: raw body, constant-time HMAC compare, replay window, fast 2xx.
- Ramp up API traffic gradually: pace Sume submits to the write budget
OpenAI now returns a slow_down 429 when traffic grows too fast. On Sume, pace paid submits to your plan's write budget and read ratelimit-remaining.
Written by Sume