question

The down behaviours dispatch task sequences of predetermined length (based on time table) to the operator. These get added to the "tasksequencequeue" node in it's variables tree. You can delete or adjust those task sequences at will using code.

I wrote some code for your sample model that gets run before the processing task finished. It checks how much time is left until the end of shift (5pm). Then is runs through all pending tasks. If there isn't enough time to finish the task, the duration of the task will get adjusted down to only last until end of shift. Any further tasks get deleted.

If the remaining time until the end of shift is negative (already ended), all tasks but the last (which should be the "home" task get deleted). The home task duration gets adjusted to end at 7am on the next day.

flexsim-help-cancel-outstanding-cumulative-downtime_fm.fsm

Note: The code assumes all pending tasks were created by the down behaviours and as such involve a travel task first and a delay task second, the duration of which is stored in "var1". If you want to manipulate the task queue in a larger model you might have to include checks to differentiate between different types of pending task sequences.