What would you like to be added
Cross-cutting data attached to a workflow instance by WorkflowExecutionListener should survive process
restarts when persistence is enabled.
Why is this needed
When a workflow instance is resumed after a JVM restart, any data that lifecycle listeners
previously associated with that instance is lost. This breaks use cases where listeners need
continuity across restarts — such as keeping a distributed trace connected across the full lifetime
of a workflow, maintaining a correlation ID. There is currently no
supported way to preserve this kind of data through a restart without polluting the workflow's own
data model with infrastructure concerns.
What would you like to be added
Cross-cutting data attached to a workflow instance by
WorkflowExecutionListenershould survive processrestarts when persistence is enabled.
Why is this needed
When a workflow instance is resumed after a JVM restart, any data that lifecycle listeners
previously associated with that instance is lost. This breaks use cases where listeners need
continuity across restarts — such as keeping a distributed trace connected across the full lifetime
of a workflow, maintaining a correlation ID. There is currently no
supported way to preserve this kind of data through a restart without polluting the workflow's own
data model with infrastructure concerns.