A finance analyst launched an invoice-triage agent that pauses to request approval before posting to the ledger. The run is waiting, the queue is growing, and she must guide it without losing progress. Which in-run interaction should the analyst use to guide the running agentic workflow?
Select an answer to reveal the explanation.
Short Explanation
You can give the waiting run a clear nudge without losing its place. Use checkpoints to review or correct details right where the workflow paused, then resume it.
Full Explanation
Open the run view, inspect the pending checkpoint, and submit approval with any corrected fields. A human-in-the-loop checkpoint pauses execution until an authorized approval resumes it, preserving ledger context, queue position, and audit trail without reprocessing. Sending a follow-up chat message with corrected invoice data can guide an active agent, but conversational input does not satisfy the gated approval requirement, so the run remains blocked. Duplicating the waiting run with corrected approval fields may help with recovery or testing, but it leaves the original execution state untouched and creates a divergent run, risking lost progress or duplicate postings. Updating the approval policy in the builder can improve handling of similar future invoices, but a workflow definition change does not disposition the live paused run. Exam caveat: distinguish resuming after approval from prompting the agent or changing its workflow; approval, queue growth, and preserving progress point to checkpoint resumption. Practical check: verify the run ID, checkpoint details, corrected ledger fields, and resume event in the history to confirm the same run continued.