The looping case review
A media service desk sees its case review fail in Debug. The canvas loops through open cases, but the body connector points back to the Loop element itself. The trace reports a cycle rather than finishing a finite iteration.
Inspect the failure, repair the connector, keep Closed cases out of the collection, and prove that a completed debug run does not mean every case should be reopened or escalated forever.
You own the complete flow incident handoff described in the brief. The next person needs working configuration and enough evidence to explain its behavior. Start with the business requirement, then keep each completed part while you add the next one. Your own saved state carries between steps.
A later task can expose a mistake that an isolated form would hide. A queue may exist without usable membership, a report may have the right title but the wrong population, and a rule may work for the example while rejecting an allowed record. Test those boundaries as you go. The final step asks for the operational conclusion or completed deliverable, and the checker keeps earlier requirements in scope.
Business requirement → configuration → boundary tests → handoff
Build a connected deliverable and retain its controls.