Recoverable dispatch handoff
Juniper's dispatch coordinator needs a visible recovery path and a per-request support handoff.
Use the fictional connector failure fixture. Keep the normal dispatch effect on success, alert Support on failure, record an audit checkpoint for either outcome, save the reference and notify the support owner.
Juniper Dispatch has a connector that sometimes fails during the dispatch handoff. Support needs an explicit recovery message and an audit record for every run, including successful ones. Build a Try and Catch pattern, then add the durable context that makes the incident usable.
The hidden fixture fails the dispatch email. It must not produce the normal acceptance email, but the support route must still complete and leave the same request identity in the audit file. A later step records that the local recovery review is complete without claiming the failed dispatch was accepted. Every effect stays inside the fixture. The finished routine separates evidence of the failed attempt from the support work that handled it, which helps the next operator avoid repeating a write without first checking its outcome.
Cloud flow: Recoverable dispatch handoff
Trigger: Manually trigger a flow
Scope [try]
Send an email (V2) [try_send]
To: dispatch@example.test
Subject: Dispatch
Body: Dispatch accepted
Scope [catch]
Run after try: Failed, TimedOut
Post message in a chat or channel [recover]
Channel: Support
Message: Dispatch needs review
The failed dispatch remains visible while Catch handles its escalation.