Workflows can run synchronously (the caller waits for completion) or asynchronously (the caller gets anDocumentation Index
Fetch the complete documentation index at: https://docs.anyreach.ai/llms.txt
Use this file to discover all available pages before exploring further.
execution_id immediately and the workflow runs in the background).
At a glance
| Sync | Async | |
|---|---|---|
| Caller behavior | Waits for completion | Returns immediately with execution_id |
| Wait steps | Block the caller (avoid) | Suspend the execution (works correctly) |
| Max duration | ~60s practical limit | Up to the workflow’s configured timeout (default 1 hour) |
| Retries | Not supported | Configurable per workflow |
| Used by | Agent tools, Ongoing Conversation | Timer, External Apps, Post Call, batch jobs |
When to use sync
- The caller needs the result immediately (agent tool during a live call)
- Total expected duration is well under 30 seconds
- No Wait steps
- Low-latency response matters
When to use async
- The workflow has Wait steps
- Total duration could exceed 30 seconds
- Retry on failure matters
- The caller doesn’t need the result synchronously
- High-concurrency batch processing

