ExplanationApplies to: All deployments
AgentFlow’s runtime, the harness around the model, handles four classes of state:
Where it lives
Redis coordinates live activity. Configured durable storage keeps product assets and history. See Architecture.
Because of this split, a client can disconnect and reattach to an active chat stream, and a direct workflow run continues as a detached run. A paused run, such as one waiting for human input, resumes from durable state.Last modified on November 3, 2026