Schedules
Pause a schedule or cancel its running task?
Future submissions and accepted work are distinct.
OfficeCubs · · 2 min read
Future submissions and accepted work are distinct. Stop the relevant layer, then inspect the other one so work does not continue or recur unexpectedly.
Compare the practical differences
| Decision | Disable schedule | Cancel task |
|---|---|---|
| Best fit | Prevent future automatic submissions | Stop a specific active execution |
| Useful property | Keeps the schedule available for later editing | Targets work already underway |
| What to check | Does not automatically undo accepted tasks | Does not disable its recurring schedule |
A concrete choice
During a broken-source investigation, disable the schedule and separately decide whether the current task should finish or stop.
Verify the choice
Check the schedule state and Task board after the action, then inspect any partial files left by cancellation.
Write the reason for your choice into the task brief or setup notes. Then run a small representative task and compare the actual result with the requirement that drove the decision. Keep any unmet requirement visible rather than declaring the whole workflow ready from a single successful step.
Continue with the setup
The related desktop guide explains the relevant controls and limits. Use the current application state when applying this comparison; the presence of an option in a document does not mean every dependency on your computer is ready.