Unfortunately I have not found a way to force the workflow to be reset at the start. This only seems to work with KNIME server. And well maybe this is a step of productivity KNIME wants you to actually pay for.
It might be possible to use a cron job on Unix/Linux that calls a batch version of KNIME to achieve something similar. But I have no real experience with that.
What does work is to have a parent workflow that calls sub-workflows which are in a reset state at the beginning. With the call structure you might be able to have some indicator that the workflow is finished and if it stopped in an unfinished mode you could restart at a specific workflow but still all of them would not be in a saved state. Although during the time of execution you could open them and see what is going on.
I have thought about a way to connect all nodes within one workflow to a node I could sort of force to do something regardless of how it is called but have not been successful with my imagination.
A simple example of a sub-workflow structure being called can be found here: