A Make scenario can update a customer successfully and fail on the following notification. Preserve the completed step and recover the missing effect rather than repeating the entire business operation blindly.
Partial failure needs step-level meaning
Partial failure means some intended effects completed while others failed, remain pending, or have unknown outcomes. A single scenario label cannot replace the authoritative state of external systems.
Make’s incomplete-executions documentation describes storing unfinished runs when that feature is enabled and options for handling them. The setting and available recovery behaviour must be checked for the actual scenario and account.
For a proposed demonstration, give consequential steps stable operation identities and record their domain outcomes outside transient execution memory where needed. Define which step establishes the business commitment and which effects can be retried independently.
Reproduce a fictional mixed result
A scenario creates a service request, links it to the customer, then fails to send a staff email. The request remains valid. Recovery should target the notification and keep its identity, not create a second request as part of a full replay.
A harder fixture loses the request-create response after the external service commits. The scenario now has an uncertain effect, not a known failed write. Reconcile before retrying, regardless of how the execution interface labels the interruption.
| Step state | Recovery rule |
|---|---|
| Write completed | Preserve authoritative record reference |
| Notification failed before send | Eligible independent retry |
| Send outcome unknown | Reconcile or apply supported duplicate protection |
| Customer mapping rejected | Resolve the relationship before continuation |
| Staff changed record later | Protect newer authorised state |
Use a fake target service and notification sink to assert final records and side-effect counts. A scenario finishing green after recovery does not prove it avoided duplicate external work.
Keep operational recovery explicit
Document which incomplete executions staff may resume, which need reconciliation, and which require engineering. Include safe evidence references and ownership. Do not make “retry” the only available response to every partial result.
Durable step tracking adds complexity to a visual workflow. That may be justified for consequential effects; simpler low-impact workflows can choose a lighter policy with explicit limits. The important point is to align the promised behaviour with the actual external contracts.
This scenario is proposed, not a claimed Make deployment. The voice integration case study describes related business-system work. Pair it with partial-success workflow design.
Make partial-failure FAQ
Does scenario rollback undo every external action?
Do not assume so. Verify each connector and external operation’s actual semantics.
Should the whole scenario be rerun?
Only when the defined operation identities and state make that safe.
What proves recovery is complete?
The intended business state is verified, duplicate effects are absent, and unresolved consequences have an accountable disposition.