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

When tasks in db are renamed, the old task stays in scheduler and still runs on same predecessor #78

Open
jeffshumphreys opened this issue Mar 23, 2024 · 0 comments
Assignees
Labels
bug Something isn't working design flaw Not a bug as much as a weakness blocking any adoption

Comments

@jeffshumphreys
Copy link
Owner

Might even cause downstream stuff to trigger twice since they now are predecessors of the same task!

Example was 1) extract_genres_from_directories and 2) extract_genres_from_file_directories. Ugh.

Solution 1: Delete all tasks in scheduler first, per run set/folder.
Solution 2:Just delete ones not in database. Maybe keep old name, and mark delete? So as to find?

@jeffshumphreys jeffshumphreys added bug Something isn't working design flaw Not a bug as much as a weakness blocking any adoption labels Mar 23, 2024
@jeffshumphreys jeffshumphreys added this to the file work complete milestone Mar 23, 2024
@jeffshumphreys jeffshumphreys self-assigned this Mar 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working design flaw Not a bug as much as a weakness blocking any adoption
Projects
Development

No branches or pull requests

1 participant