QuestionQ70

VerifiedImplement generative AI and agentic solutions

You have a Microsoft Foundry project containing a support-ticket triage agent built with Foundry Agent Service.

The agent uses a tool to classify the ticket type and set the ticket priority.

Sometimes the same support case spans multiple sessions over several days.

You need to persist state using a durable ID so that the agent automatically reuses the complete interaction history. The solution must retain previous user messages, tool calls, and tool outputs across turns and across sessions.

Which runtime component should you use?

Explanation

The conversation object in Foundry Agent Service is the durable, server-side record—identified by a conversation ID—that stores the full interaction history, including user messages, tool calls, and tool outputs. Because it is persisted independently of any single session (stored durably, e.g., in Cosmos DB), referencing the same conversation ID in later requests, even days later, lets the agent automatically pull in and continue from the entire prior history without the caller needing to resend it. This satisfies the requirement for a durable ID that preserves full context across turns and sessions, distinguishing it from an agent (the reusable definition of instructions/tools/model), a response (a single generation turn's output), or an output item (an individual message or tool-call entry within a response).

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!