A permitting workflow finds the parcel successfully but the fee service fails. How should the agent handle that partial multi-tool success?
Select an answer to reveal the explanation.
Short Explanation
Parcel found, fees missing—that’s a half-built sandwich, not lunch. Tell the resident what’s done and what’s blocked; don’t declare the permit ready. Random fees or hiding the good parcel result both make things worse.
Full Explanation
Permitting workflows often succeed on parcel lookup while fee retrieval fails—partial multi-tool success. The agent should report that progress honestly, retain the valid parcel result, and avoid claiming the permit is ready until fee retrieval succeeds or a governed fallback completes. Announcing full readiness from any single tool success, discarding good parcel data, or charging a random fee all corrupt municipal process integrity and resident expectations.
Announcing that the permit is fully ready because any single tool success is enough fails by concept: readiness is a conjunction of required steps, not a single green light. Discarding the valid parcel result and pretending the address was never found wastes correct work and forces unnecessary re-entry. Charging a random fee so the workflow can mark completion anyway fabricates financial data and creates cashiering discrepancies.
Exam caveat: define explicit workflow state machines for partial success (parcel_ok_fee_pending) so UI and staff queues show the same truth the agent speaks. Governed fallbacks might include deferred fee calculation with clear provisional labeling—not silent completion.
Operational check: in staging, succeed parcel tools and fail fee tools deliberately; confirm the agent states partial progress, retains parcel identifiers for retry, and withholds “permit ready” / payment-complete claims until fees resolve through the real tool or an approved fallback path.