A workflow can create a valid appointment and still fail to send its confirmation. Report each outcome separately so the assistant does not repeat the booking or tell the caller that everything failed.
Partial success is a first-class outcome
Partial success occurs when some steps in a requested workflow complete and others do not. It is common when a workflow spans independent systems that cannot share one transaction. A single success boolean cannot describe that state accurately.
In a proposed booking workflow, track appointment creation, customer-record linking, and notification delivery as separate operations. Give each step an identifier and an authoritative status. Define which step establishes the business commitment and which steps can be retried independently.
Do not let the model infer aggregate completion from the last tool response. The workflow service should return a structured summary showing completed, pending, failed, and uncertain steps, together with the permitted recovery path.
Follow a fictional mixed result
The booking service creates appointment A-29. The customer link succeeds. The email service is unavailable. The correct caller message is that the appointment exists and its email confirmation has not yet been sent, subject to the actual evidence returned.
Retrying the entire workflow could create a second appointment. Instead, retry the notification under its own duplicate-protection rules. If the appointment creation status is unknown rather than confirmed, reconcile that status before deciding which downstream work may proceed.
| Step combination | Required response |
|---|---|
| Booking complete, email failed | Preserve booking; recover notification |
| Booking rejected, email not started | Offer alternatives without confirmation |
| Booking unknown | Reconcile before claiming a result |
| Customer link failed after booking | Route the orphaned record for repair |
| Notification delivered twice | Record a duplicate-effect defect |
Test recovery after a worker restart. The workflow must reconstruct completed steps from durable state rather than replay every action because in-memory progress disappeared.
Choose the commitment boundary deliberately
Some businesses treat a saved request as an intake record, while an appointment requires separate staff approval. Others commit immediately when capacity is reserved. The assistant’s wording must reflect the actual business boundary.
Durable orchestration adds storage and reconciliation work. A simpler sequence may be enough for low-impact tasks, but it still needs accurate outcome reporting. Avoid making a fully atomic promise across services that cannot support one.
This design is proposed. The HVAC case study explicitly distinguishes a saved service request from a confirmed appointment and describes notification retry states. Review tool error wording for caller-facing responses.
Partial-success FAQ
Should one failed step invalidate every completed step?
Only if the business workflow defines that compensation and can perform it safely.
Can the assistant say “done” after the main write?
It should specify what completed and disclose any consequential outstanding step.
How should retries resume?
Use the durable workflow ledger and step identifiers to retry only eligible incomplete work.