Inspectable operations handoff
Birch Lane's operations lead needs a maintainable report handoff.
Read Requests, report source and Open counts, post included IDs, create /Reports/handoff.txt with recovery to Support, and send the event reference to the maintainer. Add maintainer@example.test as a co-owner in the final step.
Birch Lane needs an inspectable request report that another maintainer can own. Build source and inclusion counts, preserve the references behind the report, and put the file write behind a visible recovery route. The final handoff includes a named co-owner rather than relying on the original builder forever.
The hidden run fails report creation. Its Support message must appear, its normal file effect must be absent, and its audit email must still identify the request. The final step changes sharing settings while preserving the workflow you already tested. The local labels do not create real account permissions; they record the intended configuration. A workplace handoff would also validate the maintainer's access and connection continuity in the chosen environment. Keep the difference between a successfully handled incident and a successfully written report visible.
Cloud flow: Inspectable operations handoff
Trigger: Manually trigger a flow
Get items [source]
List name: Requests
Send an email (V2) [source_email]
To: lead@example.test
Subject: Source count
Body: @string(length(body('source')?['value']))
The source count describes every available tracking item.