The saved coroutine state is an implicitly-defined data structure and they don’t support any kind of migration when the code changes, so the durability will be quite limited.
The durable coroutine library is one part of a larger system we're releasing soon. See https://stealthrocket.tech/blog/fairy-tales-of-workflow-orch... for more information :)
As you can imagine there are a lot of challenges with it, but ideas are welcome!
This seems like a situation where defining the data structure in two different ways might be good?