In the dashboard you each task would have a URL for each of your environments. Then you can use this URL in 3rd party products. Any data in the body of the request to that URL would come through to the task as the payload.

mattaitken almost 2 years ago

17

You can fully self-host Trigger.dev. This is a really good option in lots of situations if you’re experienced with setting up and managing infrastructure. Another option would be if we offered self-hosted workers. You would host them inside your own cloud account (or on-prem) and they would connect to the Trigger.dev cloud. The pricing model for this is TBD, but it would probably be a combination of a cost per connected worker server and an invocation cost that is higher than the managed worker one.

mattaitken almost 2 years ago

10

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.

An Anonymous User almost 2 years ago

10

When you trigger a prod or staging run in the Trigger.dev cloud it takes 3 seconds on average for the machine to start up and your code to start executing. This same slowness happens when a run resumes, like after using wait.for if the delay is above a threshold when we shut the machine down. They take this long because we're using Kubernetes for our cluster and a new pod takes a while to come up. We're switching to using MicroVMs for the cloud machines. Our target is to get the p95 for starts and resumes to under 500ms.

Linear about 2 years ago

18

It’s currently difficult to diagnose performance issues. It would be useful to have graphs on the run page. This would also make it possible to find memory leaks. Currently you have to use Node functions to log out the memory: const memory = process.memoryUsage(); logger.log(“Memory usage”, memory);

mattaitken over 1 year ago

1

Please reintroduce the events feature in V3, similar to what was available in V2. Trigger with an event name and payload A task can subscribe to a named event with a filter (it will only create a run if the filter matches) A single event can trigger many tasks if it matches many

An Anonymous User almost 2 years ago

11

Currently all our machines are evenly balanced between CPU or RAM (or some of them have double the RAM than vCPU). We could add a set of CPU-optimized machines (e.g. 1vCPU + 0.25GB RAM) and memory optimized machines (e.g. 0.25vCPU + 1GB RAM). What do people think? What combos would be useful?

An Anonymous User almost 2 years ago

2

This feature will follow on from our Python extension to allow full Python support in Trigger.dev.

James over 1 year ago

8

Would be cool to unit test: have a way to unit test specific tasks and mock other other tasks (that are used within the tested task) e2e test: have a way to spin up a instance for e2e tests locally (programmatically for jest/bun testing) and tear it down after tests ran

An Anonymous User almost 2 years ago

3

Workers in Asia will reduce the latency when accessing your regional resources from your tasks.

mattaitken over 1 year ago

2

Support for logs to be sent from Trigger.dev to 1+ other destinations. We would probably start with an HTTP POST request with a JSON body, similar to how Supabase do this.

mattaitken over 1 year ago

1

Right now, multiple trigger dev instances for the same project share one queue, so any instance can run any task and they end up “stealing” each other’s work. The ask is to support something like preview branches, but for the dev environment: separate dev sessions (e.g. a session id or “dev branch”) so each local instance only runs tasks triggered from that same session. That would let you run several work trees or app copies in parallel (e.g. with Codex/Claude) without tasks from one ending up running in another.

Iss Haddad 3 months ago

1

Trigger.dev currently does not support “offline” dev mode, where you can run tasks without an internet connection. Please let us know if this is a feature you want/need. This would be great to have, and would compliment a Supabase/Next.js stack nicely. I am online 99% of the time but it would be great to develop fully locally in that last 1% where I’m at an airport or in a cafe with bad wifi.

Zachary Keener over 1 year ago

3

I recently tried to find a run by filtering on a value of the payload but I couldn’t figure out how. It would be great to be able to do something like “get be runs where task = X and payload.customerId = Y”

Rich Turnbull 8 months ago

1

These tools typically require code to be inserted extremely early in the code execution order because they automatically instrument other modules. It might be technically possible to write an ESBuild plugin that works with Trigger.dev (we support those via extensions) but it won’t be trivial. We should add an easy way to use these tools.

mattaitken over 1 year ago

5

This would allow for being able to have a concurrency limit on the entire queue, lets say 10, but each concurrency key only gets lets say 1 at a time. So the queue would never been executing more than 10 at once, and each concurrency key would only ever execute 1 in parallel. See this real world use-case: https://x.com/euboid/status/1929470623191101613

Eric Allam about 1 year ago

At the moment all users in your team are admins, which means they can all view the API keys, deploy, add/remove team members, and create/edit/view/delete environment variables. We need to add a permissions system so this can be configured by admins.

mattaitken over 1 year ago

Support for being able to write your tasks in Golang

An Anonymous User over 1 year ago

1