Has anyone encountered this error: Flow execution not found

[DianaBTX]

We have requests that are running longer an a year and we are receiving this error when trying to look at the flow that should be running for the request.   Has anyone else encountered this and if so, what did you do to resolve the issue?

[DianaBTX · Accepted solution]

thank you everyone for your help.   i recreated the flow

[Tanushree Maiti]

Hi  @DianaBTX 

Flow reporting is disabled by default due to its potential impact on instance performance. 

When flow reporting is not enabled for a specific flow, no Flow Operation History records are generated or stored for that flow's executions.

Resolution

Enable flow reporting for the target flow to begin generating Flow Operation History records:

1. Navigate to All > Process Automation > Flow Administration > Settings.
2. Click New to create a new flow reporting configuration.
3. Select the flow for which you want to activate reporting.
4. Select the desired reporting level.

Refer KB : KB1801069 Unable to Find Flow Operation History 

Flow reports not available. Check system property com.snc.process_flow.reporting.level

Also check  this system property:

https://www.servicenow.com/docs/r/build-workflows/workflow-studio/flow-designer-system-properties.ht...

el of reporting data generated by the flow engine. com.snc.process_flow.reporting.level

Specify when Workflow Studio generates execution details and what information the details include. Options include: Off The system doesn't generate flow execution details. The system only generates execution details when you run a test. Note: Testing an action or flow generates execution details at the Trace level. Basic: Runtime states and durations only The system generates runtime execution details for each flow, subflow, and action run. You can see the runtime state and duration for these basic items. You can also see configuration and runtime values for flow triggers, subflow inputs, and subflow outputs. Full: Action configuration and runtime values (for debugging only) The system generates configuration and runtime execution details for each flow, subflow, and action run. You can see the runtime state, duration, input values, and output values for all items. For custom actions, you can also see the runtime state, duration, input values, and output values of its steps. You can also see the configuration values for flow triggers, subflows, actions, and steps that are part of a custom action. Important: Only users with the fd_read_operations_all role can see configuration and runtime information such as record values in the flow execution details. Users without this role will only see basic details about the state and duration. Trace: All values (for testing and Support only) The system generates configuration and runtime execution details for each flow, subflow, action, and step run. You can see the runtime state, duration, input values, and output values for all items. You can also see the configuration values for flow triggers, subflows, actions, and steps. Important: Only users with the fd_read_operations_all role can see configuration and runtime information such as record values in the flow execution details. Users without this role will only see basic details about the state and duration. Testing an action or flow generates execution details at the Trace level. The reporting level determines what if any flow execution details are generated. If a flow runs while reporting is off, execution details are never available for the flow, even if the reporting level later changes. If a flow runs while reporting is activated, execution details are always available for that flow execution, even if the reporting level later changes. Type: choice Default value: Off Location: Process Automation > Properties More information: Flow execution details

[yashkamde]

Hello @DianaBTX ,

are you pointing to this type of error :

If yes then navigate to Flow Reporting Settings :

select -> Full: All configuration and runtime values..

If my response helped mark as helpful and accept the solution.

[AJ_01]

Hi @DianaBTX ,

Please check your instance's auto-flush rules and the associated flow contexts. Ensure that flow contexts in active states (for example, In Progress) do not have auto-flush rules configured, or that the retention period is set to more than 1 year (31,536,000 seconds). Auto-flush rules may be prematurely deleting the flow contexts required for processing, which could be causing the issue.

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.

Regards.

[Aditya_hublikar]

Hello  @DianaBTX ,

Please check its flow reportimg settings :

Set it to full