Having Issue with a Flow Not Executing

[terrieb]

Just built a new catalog item that will be opened to all employees, with and without a role within service now.

I adjusted the flow properties to Run as System User.  I asked a staff member, who has the itil role, to create a test record.

The flow failed.  It generated the Request/RITM but did not populate fields from the flow and did not create the first catalog task, so it stalled.

However, if I do a "Test" on the failed RITM record as Admin, it works just fine.

Any one know why this is happening?  Anyone have a resolution?  I tried changing it back to the default advanced property of User who Initiates Session, but it fails then as well.

Doing this in our Dev instance, which is on the current release, but it will be uploaded to our Production environment later this month, which is still on Washington DC release.

see screen shots in attachment.

Thanks!

[Uncle Rob · Accepted solution]

Ok, this is a long shot BUT... 
One thing that surprised me in my early ServiceNow days is that RITMS are created an instant before the Request is.  Its kind of like RITM is the gift, then the sc_request is the gift wrap.  You can't wrap what you don't already have.

This error seems to be complaining that the record you want to update isn't a valid GlideRecord.  Like maybe its not fully formed yet?

For the sheer giggles of it, I wonder what would happen if you put a 1 minute delay between the first and second actions on the flow.  Just to give it time to wrap the RITM in a Request with loving care.

[terrieb]

Yes that worked!  Thank you!

[Uncle Rob]