Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TRI-2314] Changing a Job the version and disabling at the same time doesn't disable the Job (v2) #1041

Open
matt-aitken opened this issue Apr 18, 2024 · 0 comments
Labels
v2 A bug associated with v2 of Trigger.dev

Comments

@matt-aitken
Copy link
Member

matt-aitken commented Apr 18, 2024

Steps to reproduce

  1. Take an existing Job that is visible and enabled in the dashboard
  2. Change the version and set enabled: false in your code
  3. Run the CLI dev command npx @trigger.dev/cli@latest dev and/or push to prod and follow the deployments guide so indexing happens
  4. It won't get disabled in the dashboard

Workaround

  1. Increase the version number and set enabled: true
  2. Index the Job by running the dev CLI and/or deploying
  3. Then set enabled: false
  4. Index the Job by running the dev CLI and/or deploying.

Fix

It should get disabled. I think this is happening because when a Job is disabled the versions are ignored.

TRI-2314

@matt-aitken matt-aitken added the v2 A bug associated with v2 of Trigger.dev label Apr 18, 2024
@matt-aitken matt-aitken changed the title Changing a Job the version and disabling at the same time doesn't disable the Job (v2) [TRI-2314] Changing a Job the version and disabling at the same time doesn't disable the Job (v2) Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v2 A bug associated with v2 of Trigger.dev
Projects
None yet
Development

No branches or pull requests

1 participant