Looking to cap your monthly spend? That’s a setting you control, not a platform limit — see
Billing limits and alerts.
Concurrency limits
Extra concurrency above the Pro tier limit is available via the dashboard. Click the “Concurrency” page from the left sidebar when on the Pro plan to purchase more.
Rate limits
Generally speaking each SDK call is an API call.
You can request a higher rate limit from us if you’re on a paid plan.
The most common cause of hitting the API rate limit is if you’re calling
trigger() on a task in a loop, instead of doing this use batchTrigger() which will trigger multiple tasks in a single API call. You can have up to 1,000 tasks in a single batch trigger call with SDK 4.3.1+ (500 in prior versions).
Queued tasks
The maximum number of runs that can be queued per queue (not across all queues in the environment). Each queue can hold up to its limit independently. When a queue hits its limit, new triggers to that queue are rejected.The limits below apply to Trigger.dev Cloud. If you self-host Trigger.dev, queue size limits are configurable via the
MAXIMUM_DEV_QUEUE_SIZE and MAXIMUM_DEPLOYED_QUEUE_SIZE environment variables — see Self-hosting environment variables.Maximum run TTL
On Trigger.dev Cloud, all runs have an enforced maximum TTL of 14 days. Runs without an explicit TTL automatically receive the 14-day TTL; runs with a TTL longer than 14 days are clamped to 14 days. This prevents queued runs from accumulating indefinitely. If you self-host, you can configure a maximum TTL via theRUN_ENGINE_DEFAULT_MAX_TTL environment variable — see Self-hosting environment variables.
Schedules
Additional bundles above the Pro tier are available for $10/month per 1,000 schedules. Contact us via email or Discord to request more.
When attaching schedules to tasks we strongly recommend you add them in our dashboard if they’re “static”. That way you can control them easily per environment.
If you add them dynamically using code make sure you add a
deduplicationKey so you don’t add the same schedule to a task multiple times. If you don’t your task will get triggered multiple times, it will cost you more, and you will hit the limit.
If you’re creating schedules for your user you will definitely need to request more schedules from us.
Projects
Each project receives its own concurrency allocation. If you need to support multiple tenants with the same codebase but different environment variables, see the Multi-tenant applications section for a recommended workaround.
Preview branches
Additional bundles above the Pro tier are available for $10/month per preview branch. Contact us via email or Discord to request more.
Realtime connections
Additional bundles are available for $10/month per 100 concurrent connections. Contact us via email or Discord to request more.
Task payloads and outputs
Large payloads and outputs are offloaded to object storage automatically. You don’t need to do anything to handle this in your tasks, as we upload and download the data transparently during operation.
On the way in, the SDK uploads any trigger or batch-item payload over 128KB to object storage before sending, so large triggers and batches don’t exceed the request body limit.
trigger and triggerAndWait have done this since SDK 4.5.0, and batchTrigger and batchTriggerAndWait (including the by-id and by-task variants) do too from SDK 4.5.2.
Payloads and outputs over 512KB are kept in object storage rather than inline. Calling runs.retrieve returns that offloaded data as a presigned download URL (payloadPresignedUrl / outputPresignedUrl).
Batch size
A single batch can have a maximum of 1,000 items with SDK 4.3.1+. Prior versions are limited to 500 items.Batch trigger rate limits
Batch triggering uses a token bucket algorithm to rate limit the number of runs you can trigger per environment. Each run in a batch consumes one token.
How it works: You can burst up to your bucket size, then tokens refill at the specified rate. For example, a Free user can trigger 1,200 runs immediately, then must wait for tokens to refill (100 runs become available every 10 seconds).
When you hit batch rate limits, the SDK throws a
BatchTriggerError with isRateLimited: true.
See Handling batch trigger errors for how to detect
and react to rate limits in your code.Batch trigger processing concurrency
When you send a batch trigger, we convert it into individual runs. This limit controls the maximum number of batches being converted into runs simultaneously per environment. It is not a limit on how many batch runs can be executing at once.Log retention
Log size
We limit the size of logs to prevent oversized data potentially causing issues.Alerts
An alert destination is a single email address, Slack channel, or webhook URL that you want to send alerts to.
If you’re on the Pro plan and need more than the plan limit, you can request more by contacting us via email or Discord.
Query
Query execution is subject to the following limits:Query lookback period
The maximum time range a query can look back is based on your plan:
If your query’s time range exceeds your plan’s lookback limit, it will be automatically clipped to the maximum allowed period.
Metric widget concurrency
The number of metric widgets that can be queried concurrently per project.Machines
The default machine issmall-1x which has 0.5 vCPU and 0.5 GB of RAM. You can optionally configure a higher spec machine which will increase the cost of running the task but can also improve the performance of the task if it is CPU or memory bound.
See the machine configurations for more details.
Team members
Additional seats are available for $20/month per seat. Contact us via email or Discord to request more.