import RateLimitHitUseBatchTrigger from "/snippets/rate-limit-hit-use-batchtrigger.mdx";

You can view your current limits, quotas, and rate limit usage in real-time by visiting the Limits page in the dashboard (accessible from the left sidebar). This page shows current rate limit token availability, quota usage, and plan features for your organization.

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.

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 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.

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 the RUN_ENGINE_DEFAULT_MAX_TTL environment variable — see Self-hosting environment variables.

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.

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.

Additional bundles above the Pro tier are available for $10/month per preview branch. Contact us via email or Discord to request more.

Additional bundles are available for $10/month per 100 concurrent connections. Contact us via email or Discord to request more.

Payloads and outputs that exceed 512KB will be offloaded to object storage and a presigned URL will be provided to download the data when calling runs.retrieve. You don't need to do anything to handle this in your tasks however, as we will transparently upload/download these during operation.

A single batch can have a maximum of 1,000 items with SDK 4.3.1+. Prior versions are limited to 500 items.

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 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.

We limit the size of logs to prevent oversized data potentially causing issues.

• Span Attribute Count Limit: 256
• Log Attribute Count Limit: 256
• Span Attribute Value Length Limit: 131072 characters
• Log Attribute Value Length Limit: 131072 characters

• Span Event Count Limit: 10
• Link Count Limit: 2
• Attributes per Link Limit: 10
• Attributes per Event Limit: 10

128 KB (131,072 bytes)

• Attributes exceeding the value length limit (1028 characters) are discarded.
• If the total number of attributes exceeds 256, additional attributes are not included.

• Strings: Actual length of the string
• Numbers: 8 bytes
• Booleans: 4 bytes
• Arrays: Sum of the sizes of all elements
• Undefined or null: 0 bytes

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 execution is subject to the following limits:

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.

The number of metric widgets that can be queried concurrently per project.

The default machine is small-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.

Additional seats are available for $20/month per seat. Contact us via email or Discord to request more.