Quotas and limits
Quotas keep configuration and automation from growing without bound, so one site cannot slow down the service for everyone. This page is for site administrators. It lists the quotas, marks those that are still in development, shows where to read them, and explains the plan limits that are still planned.
Capacity quotas
Section titled “Capacity quotas”When an action would create a record past one of these limits, the request is refused with a quota_exceeded error. The error names the quota, its limit and how much is used. The check runs in the same transaction as the change, so two requests at the same moment cannot both pass.
| Quota | Limit |
|---|---|
| Custom fields on the site | 700 |
| Custom fields in one project | 200 |
| Workflows | 50 |
| Project statuses | 100 |
| Automation rules in one project In development | 100 |
| Automation secrets in one project In development | 100 |
| Attachments on one work item | 100 |
| Runs of one automation rule per hour In development | 500 |
Fixed limits of single features
Section titled “Fixed limits of single features”Some limits belong to the feature they protect.
| Limit | Value |
|---|---|
| Size of one attachment on a work item | 10 MiB |
| Options of a select field | 500 |
| Active API tokens per person | 25 |
| Work items in one CSV export | 5,000 |
Priorities, resolutions, configuration schemes, shared workflows and the rows of one CSV import have limits too. The administrator report below lists them.
Read your quotas
Section titled “Read your quotas”Site administrators see every quota in the Limits section of site administration. For each quota it shows the limit and the largest current use. That is the project, rule or work item closest to the limit. Anyone else is refused.
The same report is available from the API:
GET https://acme.orbit.inortix.com/api/v1/admin/quotasThe answer lists the quotas with their limit, used and largest, and the fixed limits separately.
Automation runs In development
Section titled “Automation runs ”An automation rule that is triggered more than 500 times in an hour does not run again in that hour. Each extra event is recorded as a skipped run with the reason hourly budget of N runs used, where N is the budget.
The site also has a monthly quota of automation runs, counted in UTC months.
- A run counts when it reached an action. A run that only checked conditions, and a skipped run, do not count.
- A run that rolls back counts nothing. Retries that give up count once, as failed.
- Site administrators get a notification once a month when the site reaches 80% and 100% of the quota.
- When the quota is used up, every run is recorded as skipped with the reason
the site used its N automation runs this month. This includes manual runs and replays. Nothing runs until the month ends. - The quota is checked when a run starts, so runs already under way may pass it by a few.
The Automation usage section of site administration shows the use of the month by project and by rule. An earlier month can be read with GET /admin/automation-usage?month=YYYY-MM. See Automation rules.
Limits of other products
Section titled “Limits of other products”Orbit Folio and Orbit Pulse have limits of their own.
- Folio files: a size limit for each file, a limit on the files of a page, and a quota for each space. See the Editor and Markdown reference.
- Pulse: retention for each project, and daily quotas with a warning share. See Usage, retention and quotas.
Plan limits Planned
Section titled “Plan limits ”The plan catalog will add limits that depend on the plan of your organization. Their numbers are on the pricing page, and they may change before launch. They are not enforced yet.
| Group | Planned limits |
|---|---|
| People | Users, free guests, service accounts |
| Storage | One quota for the whole organization, shared by all products: Pulse data, Forge repositories, packages and artifacts, Folio files and Orbit attachments. Extra storage in packs. A maximum file size. A maximum Forge repository size. |
| Forge | CI minutes and concurrent jobs on shared runners |
| Pulse | Data retention and daily intake |
| Lumen | Questions per day or per month |
| Automation | Automation runs per month |
The plans will warn at 80% and at 100% of a limit. At the limit, the action that would cross it is refused with a clear message.
Today the quotas above apply to each site. There is no storage quota shared by an organization yet. The size of a work item attachment is the fixed limit in the table above, not a plan value.