Repository navigation
Replies: 1 comment
|
The DEV and PROD entries are separate job records, so disabling the task in production will not remove the two old DEV jobs. Also, enabled: false is a disable flag, not a delete command. It makes the job eligible for deletion in the dashboard. For each unused DEV task:
Trigger.dev documents this flow here: https://trigger.dev/changelog/disable-and-delete-jobs If the goal is only to stop old queued DEV runs rather than remove the job itself, cancel or expire those runs separately; deleting a job and deleting its run history are different operations. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Me and a colleague have both run a task in dev and it's deployed, that's three tasks, we only need the prod one, why can't a free up the resource on these?
docs say
enabled: falsethat makes no sense on a prod task 🙃All reactions