Docs: Fixes incorrect concurrency pricing on the limits page #2324
Conversation
|
WalkthroughThe documentation was updated to revise the pricing and quantity information for additional concurrent runs and realtime connections above the Pro tier. The cost for additional concurrent runs was changed from "$10/month per 100 concurrent runs" to "$50/month per 50 concurrent runs." Additionally, the terminology for realtime connections was corrected from "$10/month per 100 realtime connections" to "$10/month per 100 concurrent connections" to ensure consistency with the rest of the document. No changes were made to the structure or functionality of the documentation. Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs/limits.mdx (1)
72-72: Maintain wording consistency across sectionsOther “above the Pro tier” rows (lines 46 & 62) all start with
“Additional bundles above the Pro tier are available…”.For uniformity, replace
“Additional bundles are available …”
with
-Additional bundles are available for $10/month per 100 concurrent connections. +Additional bundles above the Pro tier are available for $10/month per 100 concurrent connections.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/limits.mdx(2 hunks)
🧰 Additional context used
🧠 Learnings (1)
docs/limits.mdx (10)
Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-07-18T17:50:25.014Z
Learning: Applies to /trigger//*.{ts,tsx,js,jsx} : When using Realtime features, use the runs.subscribeToRun, runs.subscribeToRunsWithTag, and runs.subscribeToBatch APIs as shown.
Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-07-18T17:50:25.014Z
Learning: Applies to /trigger//*.{ts,tsx,js,jsx} : When using retry, queue, machine, or maxDuration options, configure them as shown in the examples for Trigger.dev tasks.
Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-07-18T17:50:25.014Z
Learning: Applies to /trigger//*.{ts,tsx,js,jsx} : The run function contains your task logic in Trigger.dev tasks.
Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-07-18T17:50:25.014Z
Learning: Applies to /trigger//*.{ts,tsx,js,jsx} : When triggering a task from backend code, use tasks.trigger, tasks.batchTrigger, or tasks.triggerAndPoll as shown in the examples.
Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-07-18T17:50:25.014Z
Learning: Applies to /trigger//*.{ts,tsx,js,jsx} : If you are able to generate an example payload for a task, do so.
Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-07-18T17:50:25.014Z
Learning: Applies to /trigger//*.{ts,tsx,js,jsx} : You MUST use @trigger.dev/sdk/v3 when writing Trigger.dev tasks.
Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-07-18T17:50:25.014Z
Learning: Applies to /trigger//*.{ts,tsx,js,jsx} : When implementing schema tasks, use schemaTask from @trigger.dev/sdk/v3 and validate payloads as shown.
Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-07-18T17:50:25.014Z
Learning: Applies to /trigger//*.{ts,tsx,js,jsx} : When implementing scheduled (cron) tasks, use schedules.task from @trigger.dev/sdk/v3 and follow the shown patterns.
Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-07-18T17:50:25.014Z
Learning: Applies to /trigger//*.{ts,tsx,js,jsx} : When triggering a task from inside another task, use yourTask.trigger, yourTask.batchTrigger, yourTask.triggerAndWait, yourTask.batchTriggerAndWait, batch.triggerAndWait, batch.triggerByTask, or batch.triggerByTaskAndWait as shown.
Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-07-18T17:50:25.014Z
Learning: Applies to /trigger//*.{ts,tsx,js,jsx} : ALWAYS generate Trigger.dev tasks using the task function from @trigger.dev/sdk/v3 and export them as shown in the correct pattern.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Analyze (javascript-typescript)
| @@ -13,7 +13,7 @@ import RateLimitHitUseBatchTrigger from "/snippets/rate-limit-hit-use-batchtrigg | |||
| | Hobby | 25 concurrent runs | | |||
| | Pro | 100+ concurrent runs | | |||
|
|
|||
| Additional bundles above the Pro tier are available for $10/month per 100 concurrent runs. Contact us via [email](https://trigger.dev/contact) or [Discord](https://trigger.dev/discord) to request more. | |||
| Additional bundles above the Pro tier are available for $50/month per 50 concurrent runs. Contact us via [email](https://trigger.dev/contact) or [Discord](https://trigger.dev/discord) to request more. | |||
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Clarify bundle size vs. base allowance
The sentence introduces “$50/month per 50 concurrent runs” bundles, while the table directly above advertises “100+ concurrent runs” for Pro.
Readers might wonder whether the first 100 runs are included for free in the Pro tier and every additional 50-run increment costs $50, or whether the entire 100 is billable.
Consider explicitly stating something like:
Additional bundles *beyond the 100 runs included in the Pro tier* are available at…to remove ambiguity.
🏁 Script executed:
#!/bin/bash
# Search the docs for older wording that may still reference "per 100 concurrent runs"
rg -n $'per 100 concurrent runs' docs | headLength of output: 45
🏁 Script executed:
#!/bin/bash
# Show the table context around "concurrent runs"
rg -n -A2 -B2 'concurrent runs' docs/limits.mdx
# Verify the exact "100+ concurrent runs" string in the Pro tier row
grep -F -n '100+ concurrent runs' docs/limits.mdxLength of output: 589
Clarify Pro tier inclusions vs. add-on bundles
The table shows the Pro tier includes 100 concurrent runs, but line 16’s current wording could be read as if all runs are billable. Let’s explicitly call out that the first 100 runs are included and only additional 50-run bundles cost $50/month.
• File: docs/limits.mdx, line 16
Additional bundles *beyond the 100 runs included in the Pro tier* are available at $50/month per 50 concurrent runs. Contact us via [email](https://trigger.dev/contact) or [Discord](https://trigger.dev/discord) to request more.🤖 Prompt for AI Agents
In docs/limits.mdx at line 16, clarify that the Pro tier includes 100 concurrent
runs and only additional bundles beyond those 100 runs are billable. Update the
sentence to explicitly state that the first 100 runs are included in the Pro
tier and additional 50-run bundles cost $50/month, to avoid confusion about
billing.
Updates the concurrency pricing to the correct $50 for bundles of 50.