github-featured/triggerdotdev--trigger.dev
2
0
Fork 0
Code Issues Pull Requests Deployments Models Agent Notes Packages Projects Releases Wiki Activity

Updated the limits page

Browse Source
This commit is contained in:
James Ritchie
2024-10-10 15:21:53 +01:00
parent 244988e212
commit ba96397f53
2 changed files with 57 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/limits.mdx
+56 -30
View File
@@ -1,51 +1,59 @@
---
title: "Limits"
description: "There are some hard and soft limits in v3 that you might hit."
description: "There are some hard and soft limits that you might hit."
---
import SoftLimit from '/snippets/soft-limit.mdx';
import RateLimitHitUseBatchTrigger from '/snippets/rate-limit-hit-use-batchtrigger.mdx';
## Concurrency limits
These are the default limits on a free account.
| Pricing tier | Limit |
|:---------------- |:-------------------- |
| Free | 5 concurrent runs |
| Hobby | 25 concurrent runs |
| Pro | 100+ concurrent runs |
| Limit | Details |
| ------------ | ------------------ |
| Organization | 10 concurrent runs |
| Environment | 5 concurrent runs |
<SoftLimit />
If you need more than 100 concurrent runs on the Pro tier, you can request more by contacting us via [email](https://trigger.dev/contact) or [Discord](https://trigger.dev/discord).
## Rate limits
| Limit | Details |
| ----- | ------------------------- |
| API | 1,500 requests per minute |
Generally speaking each SDK call is an API call.
| Limit | Details |
|:----- |:------------------------- |
| API | 1,500 requests per minute |
<RateLimitHitUseBatchTrigger/>
## Queued tasks
The number of queued tasks by environment
The number of queued tasks by environment.
| Limit | Details |
| ----- | ------------------------- |
| Dev | At most 500 |
| Staging | at most 10 million |
| Prod | at most 10 million |
| Limit | Details |
|:------- |:------------------ |
| Dev | At most 500 |
| Staging | At most 10 million |
| Prod | At most 10 million |
## Log retention
| Pricing tier | Limit |
|:---------------- |:--------- |
| Free | 1 day |
| Hobby | 7 days |
| Pro | 30 days |
## Schedules
| Limit | Details |
| --------- | ------------- |
| Schedules | 5 per project |
| Pricing tier | Limit |
|:---------------- |:-------------------- |
| Free | 5 per project |
| Hobby | 100 per project |
| Pro | 1,000+ per project |
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.
When attaching schedules to tasks we strongly recommend you add them [in our dashboard](/tasks/scheduled#attaching-schedules-in-the-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 add them [dynamically using code](/management/schedules/create) 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.
@@ -53,16 +61,34 @@ If you're creating schedules for your user you will definitely need to request m
## Task payloads and outputs
| Limit | Details |
| ---------------------- | ---------------------------------------------- |
| Single trigger payload | Must not exceed 10MB |
| Batch trigger payload | The total of all payloads must not exceed 10MB |
| Task outputs | Must not exceed 10MB |
| Limit | Details |
|:--- |:--- |
| Single trigger payload | Must not exceed 10MB |
| Batch trigger payload | The total of all payloads must not exceed 10MB |
| Task outputs | Must not exceed 10MB |
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.
### Machines
## 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 and need more than 100 alert destinations, you can request more by contacting us via [email](https://trigger.dev/contact) or [Discord](https://trigger.dev/discord).
| Pricing tier | Limit |
|:---------------- |:----------------------- |
| Free | 1 alert destination |
| Hobby | 3 alert destinations |
| Pro | 100+ alert destinations |
## Machines
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](/machines#machine-configurations) for more details.
## Team members
| Pricing tier | Limit |
|:---------------- |:----------------- |
| Free | 5 team members |
| Hobby | 5 team members |
| Pro | 25+ team members |
docs/snippets/rate-limit-hit-use-batchtrigger.mdx
+1 -1
View File
@@ -1 +1 @@
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 100 tasks in a single batch trigger call.
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 100 tasks in a single batch trigger call.