Runners
How Runners Work
Runners execute workflows either interactively (triggered from Studio) or in the background (scheduled triggers, webhooks, API calls). All runners use the same priority-based execution queue with duplicate detection.
Registration
Administrators register runners via the Hub. The system generates a Machine Key and Machine Secret. The secret is stored as a one-way cryptographic hash and shown to the administrator only once. The license enforces a total runner limit for the organization.
Heartbeat and Polling
Runners send periodic heartbeats to the Hub with CPU, memory, and disk metrics. Runners that miss heartbeats for a documented grace period are marked OFFLINE. Runners poll the Hub for assigned work on a short interval; polling pauses during execution.
Failure Handling
| Scenario | Response |
|---|---|
| Runner offline while ASSIGNED | Re-queue once, then FAILED |
| Runner offline while RUNNING | Grace period, then FAILED |
| No runner available | Mark execution FAILED after a configured timeout |
| Authentication failure | Auto-retry with exponential backoff |
Was this page helpful?
A quick signal helps us prioritise improvements.