cleandataengineering.aiAgent Harness, drawn simply
You are here: Real flows › 16 · Pausing the agent

Agent Harness Tutorial · Real flows

Flow 16: Pausing the agent

Route: Stopped. 0 model calls · 0 tool calls · 205 ms.

Open: Entra IDEntraIDOpen: PostgreSQLPostgresstateOpen: DBOSDBOSwaitsOpen: APIM → modelAPIM→ modelOpen: Claims (MCP)ClaimsMCPTHE BOXES IT PASSEDWHAT HAPPENEDBEFORE THE MESSAGEOpen: Sign-in with Microsoft EntraSign-in with Microsoft Entrazoom in ›1Rohan signs in with MicrosoftEntra ID (code flow + PKCE); thetoken stays in the pageOpen: Page opens: load the conversationPage opens: load the conversationzoom in ›2GET /opening: the newestcheckpoint is resumed if under24 h old, else a newconversationAN OPERATOR, 13:45:24az appconfig kv set agent.enabled=false (re-read by the agent within 30 s)THE MESSAGE, 40 S LATERRohan: "What's the status of claim CLM-010007?"Open: Front doorFront doorzoom in ›3body · token verifiedOpen: BLOCKED · Kill switchBLOCKED · Kill switchzoom in ›4agent.enabled = false: ruleagent.paused · nothing elserunsOpen: Save and settleSave and settlezoom in ›5message kept in a 741-charcheckpoint · outcome refused ·205 msReply: "The claims assistant is paused for now, so I cannot act on this message. It has beensaved ... Please try again later."13:46:06agent.enabled=true again
Left: the boxes this message really passed, in order; each opens its design page. Middle: the outside systems each box called, as dots on five lanes (Entra ID, PostgreSQL, DBOS, APIM in front of the model, the claims system over MCP); click a lane head to open it. Right: what happened. Grey boxes are checks, the dark box is the model, a crossed box is where something was blocked.
What it teachesPausing needs no deploy: one App Configuration key, effective within 30 seconds.

Want every detail? The long version is in the Series: this flow with real spans and payloads.