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
I have searched the existing issues before opening this feature request.
Describe the feature you would like to see.
I would like for Schedules to pause their execution/be blocked when they reach a Backup task, until the backup task has been completed. Often, I need to run commands before and after the backup has completed. Since the scheduler immediately goes to the next task (after whatever time offset you set), I cannot accurately predict when the backup will complete and run commands at the right time.
Describe the solution you'd like.
This could be a default functionality, or something that can be enabled per backup task. Essentially, a checkmark within the Backup task labelled "Make task blocking" or something along those lines would be perfect in my mind.
The solution I'm employing now is simply setting a large offset after the backup. It's possible that the backup could exceed this time though, and that leaves me uneasy.
Additional context to this request.
I tested this by running the following schedule;
The save-on command is run exactly 7 seconds after say [AUTO-BACKUP] Server backup is beginning now. World saving will be off until completion. is run, so it seems that the backup task is immediately moved on from, even though it's still running.
The text was updated successfully, but these errors were encountered:
Is there an existing feature request for this?
Describe the feature you would like to see.
I would like for Schedules to pause their execution/be blocked when they reach a Backup task, until the backup task has been completed. Often, I need to run commands before and after the backup has completed. Since the scheduler immediately goes to the next task (after whatever time offset you set), I cannot accurately predict when the backup will complete and run commands at the right time.
Describe the solution you'd like.
This could be a default functionality, or something that can be enabled per backup task. Essentially, a checkmark within the Backup task labelled "Make task blocking" or something along those lines would be perfect in my mind.
The solution I'm employing now is simply setting a large offset after the backup. It's possible that the backup could exceed this time though, and that leaves me uneasy.
Additional context to this request.
I tested this by running the following schedule;
The
save-on
command is run exactly 7 seconds aftersay [AUTO-BACKUP] Server backup is beginning now. World saving will be off until completion.
is run, so it seems that the backup task is immediately moved on from, even though it's still running.The text was updated successfully, but these errors were encountered: