Flow Designer Error : Glide Record Invalid

[Anisse Mahtat]

Hi, I have an error in my flow and i don't know how to fix this. 

The same flow has worked before.

[kmohammed]

The "Glide Record Invalid" error in ServiceNow Flow Designer typically occurs when a GlideRecord used in a flow is invalid or does not exist. This can happen for a variety of reasons, such as:

1. Incorrect table name: Ensure that the table name in the GlideRecord query is correct and that the table exists in your ServiceNow instance.

2. Missing sys_id: A GlideRecord query must have a sys_id to retrieve a specific record. If a sys_id is not provided, the GlideRecord will be invalid.

3. Incorrect query criteria: Ensure that the query criteria used in the GlideRecord are correct and will return a result.

4. Missing table permissions: Ensure that the user running the flow has the appropriate permissions to access the table specified in the GlideRecord query.

To resolve the "Glide Record Invalid" error, review the GlideRecord query and make sure that the table name is correct, the sys_id is provided, the query criteria are correct, and the user has the appropriate permissions. If the issue persists, consider reaching out to ServiceNow support for further assistance.

[Anisse Mahtat]

Thanks for your reply 🙂 @kmohammed , I'm sure i have the correct table, the good sys_id (i can find the sys_id in the XML of my record), the query are good and maybe the missing table permissions but i run this as system admin. The same was good before and now problem in glide record

[Allen Andreas]

Hello,

I believe this may be an issue of the lookup (as you are specifying an "update" to a "record" and no actual record being found). You'd want to adjust your lookup to ensure that it finds the appropriate match. You can look this up yourself by navigating to the table in question, filtering your state to whatever 11 is and then see if you can find your dot-walked trigger record that you're specifying.

Example: you're specifying the sn_hr_core_case_payroll table and the state = 11 (whatever that is)...but you're also feeding it a very specific record by using the trigger > HR Payroll Case > and the rest we cannot see, but you're specifically saying a record and then specifying a state. If no record is found, you're get the error you're seeing.

Please mark reply as Helpful/Accept Solution, if applicable. Thanks!

[Mohammad Amin]

This response might be late but it will surely help other users facing same issue in future.
Reason : System user don't have "sn_hr_core.admin" Role. just assign the "sn_hr_core.admin" Role to the system user and it will work properly.

More Insights: the HR Scoped Application is Restricted and sometime due to Security Concerns we remove HR Admin Role from the System User. and that's the cause which restricts the System user to perform operation on HR Scoped Tables.

Regards,
Mohammad Amin