Agent Memory & State
How do I separate retrieval corpus data from durable workflow state?
Host retrieval corpora and vector stores entirely outside Catalyst’s agentic durable execution layer. Catalyst, built on Dapr, manages replayable workflow state, while retrieval corpora provide static or updated context for RAG workflows; your agent logic should explicitly call these external retrieval stores instead of embedding retrieval data into persistent workflow checkpoints. A key caveat is to avoid accidentally persisting retrieval results directly into workflow checkpoint storage or related workflow state.
Was this article helpful?
Your feedback helps improve Diagrid's FAQ experience.
Keep reading
More Diagrid FAQ articles
- Agent Memory & State
How do workflow state, conversation memory, and retrieval corpora differ for AI agents?
Explain how workflow state, conversation memory, and retrieval corpora differ for AI agents, including their unique roles in durable execution systems.
- Agent Memory & State
Which agent memory and state should be included in durable execution?
Outline which types of agent memory and state are appropriate for inclusion in durable execution layers for production AI agent workloads.
- Agent Memory & State
What agent state survives a workflow crash or restart?
Explain which agent state is preserved following a workflow crash or unexpected restart, and how Catalyst manages state persistence.