Plan limits and usage
A reference for the allowances your subscription plan sets, where each one is enforced, and what the app does when you reach one.
Allowances and prices are set per plan and are shown in the app on Settings, then Billing. This page describes what the limits mean, not what the numbers are.
Metered resources
| Resource | Enforced when | Shown on the Billing page |
|---|---|---|
| Workflows | You create a workflow | Yes |
| Team members | You invite someone, or add a member directly | Yes |
| Simultaneous workflow runs | A desktop agent starts a workflow run | Yes |
| Workflow runs per billing period | A desktop agent starts a workflow run | Yes |
| Storage | You upload a file, including run output | No |
| Webhooks | You create a webhook | No, on Settings, then Webhooks |
| Organizations you own | You create another organization | No |
Hosts are not limited on any plan. Your plan meters the work your desktop agents do instead: how many workflow runs happen at once, and how many start each billing period.
Workflow run limits
Every run of a workflow by a desktop agent counts, whether it images a machine or configures one that is already deployed.
- Simultaneous workflow runs counts the runs in progress right now, including runs paused for a reboot or blocked on a step. A run stops counting when it succeeds, fails or is cancelled.
- Workflow runs per billing period counts every run started in the current billing period, whatever its result. The allowance is a monthly figure; a yearly plan allows twelve times it over the year. A managed organization's period is the calendar month.
Both are checked once, when the desktop agent starts a run:
| Situation | What happens |
|---|---|
| Simultaneous runs are at the allowance | The run does not start. The desktop agent shows "This organization's plan allows N simultaneous workflow runs. Wait for a run to finish, or upgrade the plan." |
| Runs this period have reached the allowance | The run starts, and the desktop agent shows a warning. |
| Runs this period are 20% over the allowance | The run does not start. The desktop agent shows "This organization has used its N workflow runs for this billing period. Upgrade the plan to run more." |
| The subscription isn't active (a payment is past due, or it was canceled) | The run does not start. The desktop agent shows "This organization's subscription isn't active, so new workflow runs can't start. An owner can renew it on the billing page." |
A run that has started is never stopped by these limits, so it always finishes. While it runs, the desktop agent reports its steps, output and a regular heartbeat. A run whose desktop agent stops reporting for 2 hours (because the machine lost power, for example) stops counting toward simultaneous runs and is marked failed.
A run that ended without reporting keeps its place for up to those 2 hours. When the machine's desktop agent starts a new run on its own (unattended, after a restart), its abandoned run is marked failed right away, because a desktop agent runs one workflow at a time.
These limits need desktop agent 0.2.0 or later. An older desktop agent updates itself before it can connect.
Reading a usage meter
Each meter under Usage & Limits shows the resource name, your current count against the allowance, the percentage used, and a bar.
| State | What you see |
|---|---|
| Under 80% | A blue bar and no message. |
| 80% or above | An amber bar, a warning icon, and "You're approaching your resource limit." |
| At the limit | A red bar, an alert icon, and "You've reached your resource limit. Upgrade to add more." |
| Unlimited | An infinity symbol and the word Unlimited, with no bar. |
An unlimited allowance is never metered, so it never warns.
The two run meters use their own messages. Workflow runs this billing period can go above 100% because of the 20% margin described above.
Reaching a limit
The limit is checked when you try to create the resource, not on a schedule. Existing resources are never removed for being over an allowance.
When you are at the allowance, the request is refused and the app reports that the quota was exceeded, naming the resource, your current count, the limit, and your plan. Nothing is created. To proceed, either delete something you no longer need or move to a plan with a larger allowance.
An organization with no subscription at all is treated as having a zero allowance for every metered resource.
Changing plans while over a limit
A plan change is refused before checkout opens if your current usage is above the target plan's allowances. This applies to any plan whose limits are smaller than your usage, so it is most often hit when moving down.
The workflow run limits never block a plan change: simultaneous runs end on their own, and the count of runs resets each billing period.
The message names each resource that is over, with your current count and the allowance you would be moving to. Reduce usage below every listed allowance, then start the change again.
Features that depend on your plan
Most of the app is available on every plan. These four are not:
| Feature | Without it |
|---|---|
| Webhooks | Webhooks does not appear under Settings. |
| API access | New API keys cannot be created, and existing keys are rejected with a message pointing you to billing. You can still revoke them. |
| Multi-organization management | The tools for managing other organizations do not appear. |
| Version history | A component's History tab explains how to get it instead of listing saved versions. |
Your plan also sets how many webhooks you may create, separately from whether the feature is available at all.
When there is no active subscription
An organization without an active or trialing subscription cannot reach feature pages. Those pages redirect to Settings, then Billing, and an orange dot appears on the Billing navigation item. Settings and billing pages stay reachable.
A trialing subscription counts as active. The Billing page shows Trial as the status and the trial end date in place of a renewal date.
Subscription status is shown as one of:
| Status | Meaning |
|---|---|
| Active | Paid and current. |
| Trial | In a trial period. Feature access is the same as active. |
| Past Due | A payment failed. |
| Canceled | The subscription has ended. |
Managed organizations
An organization whose billing is handled by a parent organization has no plan controls of its own. Its allowances come from what the parent has assigned it, and its Billing page shows a "Managed by" notice instead of plan cards.
If the managed organization's subscription is turned off, or the parent organization's own access lapses, the managed organization loses feature access too. Opening the app then shows the Limited access page, which says the organization doesn't have an active subscription.
Related
- Managing your subscription for changing plans and updating payment details.