I am the administrator (full permissions) and I created a record-triggered flow to create a record and update a field. In debug, the flow works without error and says the record would be created at the end of the interview. When I do the action to trigger the record-triggered flow--no record is created and the field is not updated. I have tried many things: manually loading the new field (to make sure the data fields are all correct); checking validations, workflows and other flows for interference; clearing my session cache; creating a debug log; verifying activation version; and upgrading to the latest API version. What else would cause a record to not be created in the flow? (And I can create it via data loader.)
My scenario might be different than the OP, but it fits the "works in debug, but fails in environment" classification.
In my case, I had created a flow that was cloning an existing record.
I used the system variable 'recordId' to get the record's Id, but I had made the error of using a capital D, so I entered 'recordID' as the variable name. That system variable is case sensitive.
In Debug mode, my flow would work properly because I was giving the flow the recordId to use for testing the flow.
But in environment, the flow couldn't define the record's Id (recordId), because I had named the system variable it with an improper case.
