System Log Error message: Flow Designer: No Record Found: no thrown error

Christian_
Tera Guru

This post will cover the System log Error message: Flow Designer: No Record Found: no thrown error.

 

The Error message Flow Designer: No Record Found: no thrown error, is atm. (Utah Release) very limited in information, both in what it concerns and its context.

Example to this from the System log:

Christian__0-1679643945747.png

 

Root cause

The issue is due to the use of the Action Look Up Record in a Flow Designer Flow, when the record is not found.

Christian__0-1679655899685.png

ServiceNow have a Problem (PRB1648314) for this issue, unfortunately closed: "After careful consideration of the severity of the issue and the risk of attempting a fix, we have decided not to address this issue in a current or future release".
In the future there is hope for more context to this message as well, until then the sys_flow_log will assist, see more info bellow.

 

Solution

If you want to make sure that this does not appear in the logs, then you need to change the Flows generating this, to use Look Up Records and check the count, instead of the Look Up Record Action.

Example:

Christian__1-1679656339730.png

 

If you want to locate all the Flows that generate this Error you should use table: sys_flow_log, with the following query: message=Flow Designer: No Record Found
Or this path, URL: /sys_flow_log_list.do?sysparm_query=message%3DFlow%20Designer%3A%20No%20Record%20Found&sysparm_view=
In this table ☝️ you will get more context to the message, enabling you to get an overview of the Flows that causes the error messages.

1 REPLY 1

Rafał Rataj
Tera Contributor

I love those super informative system logs 

 

Thanks for sharing!