docs: add dedicated billing limits and alerts page#4132
Conversation
|
WalkthroughThis pull request adds a new documentation page, docs/billing-limits.mdx, explaining Trigger.dev billing limits and alerts, covering setup, environment scope, alert thresholds, enforcement flow with a grace period, resumption behavior, and usage tracking. It registers this page in docs/docs.json navigation. Related docs (how-to-reduce-your-spend.mdx, limits.mdx, troubleshooting.mdx) are updated to reference or link to the new page, with prior inline explanations condensed or replaced by cross-references. Changes
Sequence Diagram(s)Not applicable — this pull request contains only documentation content changes. Related Issues: Not specified in the provided information. Related PRs: Not specified in the provided information. Suggested labels: documentation Suggested reviewers: Not specified in the provided information. 🐰 A rabbit hops through docs anew, 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: f7bf8ce0-16d1-4248-a526-dd5b4ad4a353
📒 Files selected for processing (5)
docs/billing-limits.mdxdocs/docs.jsondocs/how-to-reduce-your-spend.mdxdocs/limits.mdxdocs/troubleshooting.mdx
📜 Review details
🧰 Additional context used
📓 Path-based instructions (3)
docs/**/*.mdx
📄 CodeRabbit inference engine (docs/CLAUDE.md)
docs/**/*.mdx: MDX documentation pages must include frontmatter with title (required), description (required), and sidebarTitle (optional) in YAML format
Use Mintlify components for structured content: , , , , , , /, /
Always import from@trigger.dev/sdkin code examples (never from@trigger.dev/sdk/v3)
Code examples must be complete and runnable where possible
Use language tags in code fences:typescript,bash,json
Files:
docs/troubleshooting.mdxdocs/limits.mdxdocs/billing-limits.mdxdocs/how-to-reduce-your-spend.mdx
**/*.{ts,tsx,js,jsx,mts,cts,mjs,cjs,md,mdx}
📄 CodeRabbit inference engine (CLAUDE.md)
Always import from
@trigger.dev/sdkwhen writing Trigger.dev tasks; never use@trigger.dev/sdk/v3or deprecatedclient.defineJob.
Files:
docs/troubleshooting.mdxdocs/limits.mdxdocs/billing-limits.mdxdocs/how-to-reduce-your-spend.mdx
docs/**/docs.json
📄 CodeRabbit inference engine (docs/CLAUDE.md)
docs/**/docs.json: Main documentation config must be defined indocs.jsonwhich includes navigation structure, theme, and metadata
Navigation structure indocs.jsonshould be organized usingnavigation.dropdownswith groups and pages
Files:
docs/docs.json
🧠 Learnings (2)
📚 Learning: 2026-03-10T12:44:14.176Z
Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 3200
File: docs/config/config-file.mdx:353-368
Timestamp: 2026-03-10T12:44:14.176Z
Learning: In the trigger.dev repo, docs PRs are often companions to implementation PRs. When reviewing docs PRs (MDX files under docs/), check the PR description for any companion/related PR references and verify that the documented features exist in those companion PRs before flagging missing implementations. This ensures docs stay in sync with code changes across related PRs.
Applied to files:
docs/troubleshooting.mdxdocs/limits.mdxdocs/billing-limits.mdxdocs/how-to-reduce-your-spend.mdx
📚 Learning: 2026-04-30T20:30:29.458Z
Learnt from: ericallam
Repo: triggerdotdev/trigger.dev PR: 3226
File: docs/ai-chat/quick-start.mdx:13-13
Timestamp: 2026-04-30T20:30:29.458Z
Learning: In this repo’s documentation MDX files (`docs/**/*.mdx`), use `ts` and `tsx` (not `typescript`) as the code-fence language tags for TypeScript/TSX snippets. Do not flag `ts`/`tsx` code-fence language tags as incorrect in any docs MDX file, since this is the site-wide Mintlify-compatible convention.
Applied to files:
docs/troubleshooting.mdxdocs/limits.mdxdocs/billing-limits.mdxdocs/how-to-reduce-your-spend.mdx
🪛 LanguageTool
docs/billing-limits.mdx
[style] ~9-~9: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... approach thresholds you choose. Billing limits and alerts are available to all ...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
🔇 Additional comments (4)
docs/billing-limits.mdx (1)
1-65: LGTM!docs/docs.json (1)
258-264: LGTM!docs/how-to-reduce-your-spend.mdx (1)
27-27: LGTM!docs/limits.mdx (1)
10-13: LGTM!
| ### Runs queued because a billing limit was reached | ||
|
|
||
| If your organization has a [billing limit](/billing-limits) configured and your monthly spend reaches it, billable environments (`production`, `staging`, and `preview`) pause: new runs are still triggered and queued, but they won't start executing. Check the **Billing limits** page in your organization settings — increasing or removing the limit resumes execution. | ||
|
|
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Clarify the queued-run resume flow.
This wording suggests that raising/removing the limit automatically resumes queued runs, but the billing-limits page says users are prompted to choose whether to resume or cancel that backlog. Please make this pointer reflect that choice or link directly to the full flow.
Suggested wording
- If your organization has a billing limit configured and your monthly spend reaches it, billable environments (`production`, `staging`, and `preview`) pause: new runs are still triggered and queued, but they won't start executing. Check the **Billing limits** page in your organization settings — increasing or removing the limit resumes execution.
+ If your organization reaches a billing limit, billable environments (`production`, `staging`, and `preview`) pause: new runs still queue, but they won't start executing until you raise or remove the limit and choose whether to resume or cancel the queued runs. See [Billing limits and alerts](/billing-limits) for the full flow.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### Runs queued because a billing limit was reached | |
| If your organization has a [billing limit](/billing-limits) configured and your monthly spend reaches it, billable environments (`production`, `staging`, and `preview`) pause: new runs are still triggered and queued, but they won't start executing. Check the **Billing limits** page in your organization settings — increasing or removing the limit resumes execution. | |
| ### Runs queued because a billing limit was reached | |
| If your organization reaches a billing limit, billable environments (`production`, `staging`, and `preview`) pause: new runs still queue, but they won't start executing until you raise or remove the limit and choose whether to resume or cancel the queued runs. See [Billing limits and alerts](/billing-limits) for the full flow. |
Summary
Follow-up to the billing limits changelog release. The feature was only documented as a section inside "How to reduce your spend" (in the Troubleshooting nav group), and that section was missing several behaviors from the release: the 24-hour grace period, the Cancel in-progress runs option, that queued runs are canceled when grace expires, and the resume-or-cancel choice when raising or removing a limit.
New
/billing-limitspage covering the full billing limits feature : the three limit options (plan / custom / no limit), billing alerts (% of limit or dollar thresholds), what happens when the limit is reached, the recovery flow, the soft-limits caveat, and the billing limit marker on the Usage page.Registered under "Using the Dashboard" in the nav, next to Alerts.
QUEUEDruns