You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
first, thank you for this great tool! I have a question regarding the functionality of stopping jobs:
Is there currently a way to allow all jobs to run as defined in the config.ini and then, after their execution is complete, stop all of them through a command in the container?
Example Use Case
Jobs are scheduled and executed as defined in the config.ini.
Once all jobs have finished their respective tasks, I want to issue a command (e.g., from within the container) to stop all running jobs, ensuring that they finish their current execution but are not rescheduled.
Reason for the Question
This feature would be particularly useful in scenarios where the container needs to be updated or restarted without prematurely terminating running jobs. It would also simplify managing job lifecycle in dynamic environments.
If this feature is not available, are there any suggested workarounds to achieve this functionality?
The text was updated successfully, but these errors were encountered:
Hello,
first, thank you for this great tool! I have a question regarding the functionality of stopping jobs:
Is there currently a way to allow all jobs to run as defined in the config.ini and then, after their execution is complete, stop all of them through a command in the container?
Example Use Case
Reason for the Question
This feature would be particularly useful in scenarios where the container needs to be updated or restarted without prematurely terminating running jobs. It would also simplify managing job lifecycle in dynamic environments.
If this feature is not available, are there any suggested workarounds to achieve this functionality?
The text was updated successfully, but these errors were encountered: