Durable execution looks a bit like a buzzword in general. If your state is defined in the execution graph then it's just an umbrella name for a group of pre-existing algorithms and patterns (e.g. exactly-once transactions in bookkeeping are centuries old). If your state is undefined then what are you resuming to? The snapshot just before the crash likely leads to the undefined state again, in which case you're durably automating the crash (or even worse, uncaught incorrect behavior).