Cause of the "Glide Record is Invalid" Error

[ayano]

This flow is configured on a Catalog Item, and it is triggered when the corresponding Catalog Item is submitted.

As the first action in the flow, there is a step that updates the approval and work_notes fields on the REQ record referenced by:

Trigger - Service Catalog → Request Item Record → Request

However, this action works correctly for some Catalog Items, while for others it fails with the error "Glide Record is Invalid", as shown in the screenshot.

The sys_id shown in the flow context matches the sys_id of the correct REQ record.

My question is: why would the "Glide Record is Invalid" error occur in this situation?

I would appreciate it if you could suggest possible causes and troubleshooting approaches.

As far as I know, neither the Catalog Items that work nor the ones that fail have any special controls, business rules, or restrictions on the RITM or REQ fields.

Best Regards,

[HarishKumar6668]

Hi @ayano ,

Could you please verify the Run As flow property.If the flow is currently configured to Run As: User who initiates session, please change it to System User and test again.

I hope this helps! If this resolves your issue, please consider marking this reply as Helpful & Accept as Solution.

Regards,
Harish

[ayano]

Hi @HarishKumar6668 ,
Thank you for your comment.

I checked the flow properties.
The "Run As" setting was already configured as "System User."

Best Regards,

[OlaN]

Hi,

Two things.

1. How will that work if you submit 2 items in the same REQ ?
In theory, they will both try to access the same record and update it.

So some kind of race condition will probably happen, and only one of them can do the update.

2. The REQ is generated after the RITM is created. It might be that the flow is executing too fast and the REQ hasn't been created yet. I would try to first do an action that waits for 2 seconds to make sure the REQ has been created.

[ayano]

Hi @OlaN ,
Thank you for your comment.

How should I verify scenario #1?

Normally, this flow is triggered when a single Catalog Item is submitted. Once triggered, it retrieves the REQ record through:

Trigger - Service Catalog → Request Item Record → Request

Could you explain how I can test whether a race condition is occurring in this case?

As for scenario #2, I have already tested it.

I added a Wait for 2 seconds action before the update step, and I also moved the action that was throwing the error from the beginning of the flow (Action 1) to the middle of the flow (Action 12) to verify whether the REQ record could be retrieved from the Request field of the RITM.

However, neither change made any difference. In both cases, the result was still the same: "Glide Record is Invalid."

Best Regards,