Rate Limiting / throttling

Feature RequestJul 12, 2024

We currently support setting a concurrencyLimit on a task, or on a queue that you create. This can also be used with a concurrencyKey to have per-user queues: https://trigger.dev/docs/queue-concurrency

Sometimes instead of concurrency you want to limit using a rate. For example, 10/minute, 1/second.

This is especially useful when using APIs that have rate limits.

We should support this with a per-tenant key like we do for concurrency.

Posted by An Anonymous User · Jul 12, 2024

Planned10

Anonymous User

•

Jul 16, 2024

I wish I could upvote this one multiple times. We use various APIs to enrich data as it enters the system or gets updated in various ways… but those APIs have rate limits.

j-fdion

•

Oct 21, 2024

I’m also really interested in this, I’m currently using resend to send emails and it’s easy to hit their rate limit if you batch trigger multiple task.

aquiveal
•
Jun 8
https://github.com/aurumorinc/trigger.dev/tree/feat/add-worker-rate-limiting-support

An Anonymous User

•

Dec 6, 2024

Very interested in this. We are consuming an API that has a 100/min rate throttling. Ideally we just throttle the entire job queue and fire events as they come in, and the queue burns down at a specific velocity.

aquiveal
•
Jun 8
https://github.com/aurumorinc/trigger.dev/tree/feat/add-worker-rate-limiting-support

Ian H

•

Feb 2, 2025

This is the last feature we need to fully move all of our jobs from Inngest → Trigger.

Use case is pretty typical: Upstream service has API which has rate limiting per endpoint. Ideally we’d have single purpose job that would do API call, and we set throttle limits on it.

Would be nice to add throttle key to support rate limiting per org.