https://temporal.io/blog/durable-distributed-asyncio-event-l... explains how it works

Thanks, that would solve it! Their „workflows“ provide a nice abstraction. Though I’d rather like to not include an external service.

Imagine a simpler implementation for me where any earlier called subfunction would simply return the previous result, up to the point where the function was previously interrupted. Therefore these previous return values need to be stored (in what temporal calls a workflow), i.e. in a database. Sounds simple enough and decorators would probably help designing a good abstraction and keeping everything self-documenting and simple enough to understand.