Should I end a task-scheduler task after processing is finished?

Doublin · 31 Jan 2021

Via task scheduler, I start a program that runs some calculations and closes itself when finished.
But the task in taskscheduler is still "running" instead of being back to "ready". I have seen that this blocks other tasks from writing to a file created by the first program.
How is task scheduler intended to use? Always end a task after your processes are finished? Or just ignore that the task is "running" much longer than needed?

Matthew Wai · 31 Jan 2021

Press F5 to refresh it after the processes are finished.

Try3 · 01 Feb 2021

Task scheduler [TS] is a real pig about this.

TS immediately changes the state to Running but it needs a manual Refresh to update the status afterwards [probably to Ready].
- So either Refresh as Matthew says, or
- Close & re-open TS.

If, when you Refresh, the task is still Running but you believe that it has finished then that would be a TS fault that needed investigating.
If, when you Refresh, the task is Ready but those other tasks cannot get access then that is a problem outside of TS. That would need a different investigation.

Do you have a method for determining if your 'program' has finished and closed?
- Might it be missing a Close command?
- You haven't said what sort of 'program' it is so I cannot speculate about it.

Denis

Doublin · 01 Feb 2021

Thank you Matthew. F5 does the job. That is a somewhat surprising behavior of taskscheduler. But ok. Thanks Denis, I set an extra quit() in the end of the r-script, but thats not necessary, r closes anyway. Indeed, that case, when a file was occupied by an other process has to do outside of this task. I just want to be sure all closes and cannot produce any conflicts. Thats the case now and verified with a TS
refresh.