Resolve flow run failures that show snapshot retrieval errorsIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } When running a flow, either by Test or by triggering it, it fails to run. Checking the Node logs shows an error: Could not retrieve snapshot for test Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } All supported releases Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Flow Designer ran into difficulties executing the flow. To determine the exact cause, use the Node logs. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } In Flow Designer: Go to Flow Properties and set the log level field to Debug. Run the Flow test again to reproduce the error. Look for the error message "Could not retrieve snapshot for test" In the Node logs: Find the starting point of the log section, which begins with: DEBUG: Flow Designer: Compiling flow [flow name].Remove unrelated entries, including references to business rules, activity on different threads, or different users.To identify the failure point, review the remaining log entries (approximately 30 lines) while referencing your flow in Flow Designer. For example, consider this log stack: DEBUG: Flow Designer: Compiling flow TestFlow | Change DEBUG: Flow Designer: Step Get Catalog Variables Step Created with an input count of 3 and an output count of 0DEBUG: Flow Designer: Step Get Catalog Variables Step Created with an input count of 3 and an output count of 5DEBUG: Flow Designer: Action created with an input count of 3 an output count of 5 DEBUG: Flow Designer: Step Lookup Record step Created with an input count of 5 and an output count of 2DEBUG: Flow Designer: Step Lookup Record step Created with an input count of 5 and an output count of 2DEBUG: Flow Designer: Action created with an input count of 5 an output count of 2 DEBUG: Flow Designer: Step Create Task step Created with an input count of 4 and an output count of 2DEBUG: Flow Designer: Action created with an input count of 3 an output count of 2 DEBUG: Input param1 assigned with a reference count of 1DEBUG: Input param2 assigned with a reference count of 1 SEVERE *** ERROR *** Flow Designer: nullSEVERE *** ERROR *** Flow Designer: Could not retrieve snapshot for testcom.glide.flow_trigger.engine.FlowSnapshotPlanRetriever.retrieve(FlowSnapshotPlanRetriever.java:33)com.snc.process_flow.engine.serialization.PlanProxy.plan(PlanProxy.java:43) This stack is going through the various actions of the flow and trying to compile everything. You can check that in the flow and you'd see something like: Get Catalog Variables: OKLookup Record: OKCreate Task: OK The flow likely fails on the next step in the run. The 'null' in the error is likely a missing input value. The logs show the following inputs for the next step: DEBUG: Input param1 assigned with a reference count of 1DEBUG: Input param2 assigned with a reference count of 1 The first two (param1 and param2) work but the third one fails resulting in the null error.