Runs and quota
How each workflow evaluation is recorded, what a run detail tells you, the monthly run quota per plan, and the 50-workflow cap.
Run history
Every evaluation whose trigger matched is recorded as a run.
| Status | Meaning |
|---|---|
| Success | The workflow ran through, including actions that declined to do anything |
| Condition not met | A condition sent the run down a branch that goes nowhere |
| Failed | An action stopped the workflow |
| Loop stopped | A safeguard cut a chain of automations short |
Each run is described in one sentence saying what the workflow actually did, in plain language: which actions ran ("Ticket assigned", "Discord DM sent to 3 recipients"), and, just as importantly, which ones declined to and why ("the ticket was already assigned to that member", "the ticket is closed"). A skipped action is a normal outcome, not an error: the run still succeeds and the other branches keep going.
- A Condition not met run names the condition that stopped it, worded exactly as it appears on its card.
- A Failed run states which action stopped the workflow and why (for example, the ticket no longer exists). Technical error details stay on the server.
Each row also shows the trigger that started the run, when it ran, and how long it took, plus the ticket number, linking to the ticket when it still exists. Technical details expands the raw values each node produced, for when you need to see exactly what the workflow was working with.
Run history is kept for 90 days, and it outlives the tickets it refers to. That is why it records counts and identifiers rather than content: you will see that three recipients were notified, never who they were.
Monthly run quota
Every plan gets the full workflow builder — all triggers, conditions, and actions. Plans differ on how many times your workflows can run each month, per project:
| Plan | Automation runs / month |
|---|---|
| Free | 200 |
| Plus | 1,000 |
| Team | 10,000 |
| Enterprise | Unlimited |
A run is counted when a workflow actually executes at least one action — including a run that fails or is stopped by the loop safeguard. A workflow whose trigger fired but whose conditions filtered it out (Condition not met) costs nothing, so conditions are free to use as filters. Each answer to a customer prompt counts as one run.
The quota resets monthly on the project owner's billing anniversary (the same window as the AI response quota) and follows the project owner's plan. The Automations page shows a usage banner with the current count, and a warning appears when 80% of the quota is used.
When the quota is used up, workflows stop running for the rest of the period: new ticket events are skipped, existing tickets are untouched, and nothing is deleted. Active workflows show a Paused badge, and everything resumes automatically when the quota resets — or immediately after an upgrade.
Workflow count
Each project can hold up to 50 workflows, on every plan. This is a technical limit — the engine evaluates every active workflow on each ticket event — not a commercial one; with condition branching, a handful of workflows covers most setups.
Workflows beyond the cap (possible after transferring old data) are marked Locked and never run.