In real-world use cases, human-in-the-loop responses can often take hours or even days to arrive. Currently, the workflow server is required to keep workflow state in memory while waiting for such responses, which is inefficient and limits scalability.

We propose introducing the ability to pause (persist) a workflow’s state to the workflow store when awaiting human input, rather than holding it in memory. Once the human response event is received, the workflow should be able to resume seamlessly from the persisted state.

This enhancement would improve reliability, scalability, and fault tolerance for long-running workflows involving asynchronous human participation.