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

Changing scheduling and repetition fields leaves unwanted files in the spooler #22

Open
guglielmo opened this issue Jun 17, 2020 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@guglielmo
Copy link
Member

Whenever the scheduling fields of an already scheduled task are changed,
the old scheduled execution, re-creates a new file in the spooler with the old scheduling values.

Thus, multiple files, with different execution scheduling will live in the spooler, generating confusion and unwanted executions.

A workaround is to manually stop the task (thus removing the file in the spooler), before changing the values.

This could be also the possible solution. Whenever an update is required for a task, the task is automatically stopped before the update, so that no trailing files are left in the spooler.

@guglielmo guglielmo added the bug Something isn't working label Jun 17, 2020
@guglielmo guglielmo self-assigned this Jun 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant