Workflow runs
Monitor execution history and debug failed workflows.
Every time a workflow executes, Bringboard creates a run record with the trigger data, step results, timing, and status.
Viewing runs
Go to Settings → Automations → Runs to see all workflow runs across your org. Each row shows:
- Workflow name
- Trigger type and event
- Status (completed, failed, pending)
- Duration
- Candidate and position (when available)
- Timestamp
Click a run to see the step-by-step detail: each action's input, output, status, and duration.
Run statuses
| Status | Meaning |
|---|---|
| Completed | All actions executed successfully |
| Failed | An action encountered an error and the workflow stopped |
| Pending | The workflow is queued or in progress |
Failed runs
When a run fails, the detail view shows which action failed and the error message. Common failure causes:
- A referenced template was deleted
- The target stage doesn't exist (position pipeline changed)
- The email rate limit was exceeded
- A required field value was missing
Rate limits
Two rate limits protect against runaway automations:
- 100 workflow runs per hour per org - prevents infinite loops
- 50 workflow emails per hour per org - prevents email flooding
Rate limits are configurable. Contact support if your org has legitimate high-volume needs.
Loop prevention
Actions taken by workflows (like moving a candidate to a stage) are tagged as automation-generated. These events do not re-trigger other workflows, preventing infinite loops.