A successful branch does not establish what happens when a record action fails. A missing required value or rejected validation rule can stop a flow before the intended handoff exists. Connect the failing element to a recovery path that records the cause and gives the next owner usable evidence.
In this local model the failed element rolls back its own writes before its fault connector runs. An unhandled failure rolls back the whole flow run. Earlier valid work may remain when a fault is handled, so check that behavior deliberately. The FaultMessage resource contains the failure cause; it is not evidence that the intended creation succeeded. Keep recovery out of the success branch and compare record counts before and after the failed action.