catalog item designer flow fails to trigger correctly but test shows it should work

[chrisn_]

I have created 2 flows to operate like workflows for 2 catalog items.
The two catalog items are:
Rotate Documention
Fellowship Request

These flows are part of a new application that will include a request process. The two catalog items belong to the global application, but the flows belong to the Graduate application as it will be creating records on two custom tables.
This is what should be happening.
User submits Request using catalog item on the portal using one of these 2 requests ->REQ & RITM are created as this is a requirement to trigger the flows-->the flow creates a request record on the Graduate Request table as well as a child task for this request and populating them with the request information.--> users do their work closing the tasks. The flow will then roll up closing the request task, and the RITM task to close out the request.

When I submit a request using the catalog item on the portal the REQ & RITM records are created with the information I expect, but the Graduate Division Request record is blank, and it has no child tasks at all like it should.
If I then take this RITM record and use the test function in the flow designer to see where I went wrong it creates the records perfectly with all of their information and the flow operates as I expect. Something is wrong and I don't know where I am going wrong. I checked the scopes and the application allows access from all scopes, same with the tables. I also checked the tables permissions and I allow global to read/write/update/insert.

Why is the test function working perfectly, but all manual testing fails? To add to this I had successful tests previously but they both no longer work and I have not found any global or in scope changes that should have caused this. Does anyone have any suggestions on where I could focus my attention on this? I am still new to flow designer and could be missing something terribly obvious.

[Luke Van Epen · Accepted solution]

Try changing the Run as setting to be system instead of user who initiated the flow.

If that works and the other doesn't, there is a permissions issue with the user who is kicking off the flow in that they are unable to create/update the subsequent task records. In my experience the Test function is inconsistent with this kind of permissions checking

[chrisn_]

Thank you sir that did the trick!