Maestro user guide

Catch failure at the task and recover (error boundary)​

• A task may fail and needs manual handling at the same point.
• Retry is not desired; recovery replaces reattempt.

1. Start.

2. Service task: Process transaction, with an interrupting error boundary.

3. On error: User task Handle manually. End Resolved.

4. Normal path: Process transaction completes. End Completed.

   Note:

   Recovery happens at the point of failure.

   Other scenarios

• Finance: Invoice posting failure routes to manual entry.
• Healthcare: Insurance verification failure triggers manual follow‑up.
• Manufacturing: Automated QC failure triggers manual inspection.
• Retail: Online order submission failure routes to an agent.
• Telecom: Activation failure dispatches a field technician.

Graceful degradation with optional system fallback​

• An optional automated step might fail.
• The process can continue manually without blocking completion.

1. Start.

2. Service task: Automated quality check, with an interrupting error boundary.

3. On error: User task Manual inspection. End Checked.

4. Normal path: Automated quality check completes. End Checked.

   Note:

   Manual fallback preserves completion.

   Other scenarios

• Finance: Automatic report generation fails; produce a manual report.
• Healthcare: Insurance lookup fails; run a manual query.
• Retail: Product sync fails; update the catalog manually.
• Manufacturing: Scheduler fails; create jobs manually.
• Public sector: Automatic verification fails; perform manual review.