For Jobs to actually run, they need to be connected to the Trigger.dev platform.
The main page for a Project is the list of connected Jobs. You can see overview details for a each Job here, including details on the Trigger, Integrations and when it was last run.
The homepage of a Project
How to add your first Job
We recommend you do the initial setup of a new Project by following our quick start guide. Once completed you should have an example Job in your dashboard.
Adding more Jobs locally
When you add a new Job to your codebase, you’ll need to connect it to Trigger.dev. This is achieved by refreshing the endpoint in your local Dev environment.
- Go to the “Environments & API Keys” page for your Project
- Select the “DEV” row in the table of endpoints.
- Click the “Refresh now” button
You only need to do this when you add a new Job (a job with an ID that hasn’t been connected to Trigger.dev before). If you modify an existing Job, you don’t need to refresh the endpoint.
See our deployment guide.
Sometimes there’s a Job that you no longer want to be Triggered. You can achieve this by Disabling it. This will prevent the
run() function being called for that Job.