Tried creating the fault path through a 'Create Records' element from the Create Refund Request element but it doesn't let me move past this error.
I have created a new resource for the Subject message and assigned the caseId manually. I tried to delete the fault path and retry the element, still no luck. Anyone knows what I'm doing wrong? Appreciate the help!
When you add a fault path to Create Refund Request, the Create Records on that path must use the system fault message and the record’s Id—rather than your own custom text resources—to satisfy the verification script. Here’s exactly what to do:
1. Remove Your Custom “Subject Message” Resource
You don’t need a separate text resource for the error. The flow provides a built‐in variable:
bashCopyEdit$Flow.FaultMessage
This holds the exception text when your record‐create fails.
2. Use the Record’s Id Variable
If this is a record‐triggered flow on Case, you automatically have a resource called {!$Record.Id} (or {!recordId} in an autolaunch)—use that, not a manually created CaseId variable.
3. Wire Up the Fault Path Properly
- In Flow Builder, click your Create Refund Request element.
- In the right pane, click Add Fault Path. A red arrow appears.
- Drag that red arrow out onto the canvas and drop it on a Create Records element.
- Label it exactly Create Error Log (and let the API Name auto‐fill).
- Configure Create Error Log:
- Object: the custom error‐log object (e.g. Refund_Error__c).
- Field Mappings:
- Refund_Request__c → {!Create_Refund_Request.Id}
- Error_Message__c → $Flow.FaultMessage
- Case__c (or your Case lookup) → {!$Record.Id}
- Connect the Create Error Log element’s success arrow back to wherever your flow ends.
4. Save, Activate & Test
- Save the flow and Activate it.
- Debug with missing data so the Create Refund throws an error, and verify that a Refund_Error__c record appears with the FaultMessage and correct Case Id.
