How to get the node log entries for async flows that have executed?SummaryWhen you create a record or submit a catalog item that is expecting a flow to execute, how do you know which node picked up the async flow?Once we know which node the async flow executed, then we can review the node logsReleaseKingston and aboveInstructionswhen you create a record or submit a catalog item that is expecting an async flow to executeyou'll see a corresponding event "flow.start" in the [sysevent] tablereview the state of the sysevent record, if it shows "processed" then the FEEH (Flow Engine Event Handler) picked up the event and processed the flow[sys_flow_context] sys_id will be in the instance name of the [sysevent] recordfrom the claimed_by field of the sysevent record you can see which node picked up the flow event, then can be furthered confirmed by the sys_update_by which would show "system"with the sys_updated_on timestamp, you can now go on Splunk and search this node at this time for when the worker processed the flow eventthe node log entry would start with: 2020-02-12 12:48:49 (234) worker.2 worker.2 txid=fa621873db7e *** Start Background transaction - system, user: system2020-02-12 12:48:49 (236) worker.2 worker.2 txid=fa621873db7e Name: Flow Engine Event HandlerJob Context: If a Null Pointer Exception is found then the sys_id of the [sysevent] and [sys_flow_context record] will show, example: 2020-03-14 10:34:59 (581) worker.6 worker.6 txid=255fc3611be7 SEVERE *** ERROR *** Failed to process event: sysevent[e74f4fe91b6340100e24a717ec4bcba7], targetContext: sys_flow_context[ef4f4fe91c634010b4b2503c2a9d8da6], exception:com.snc.process_flow.exception.ProcessAutomationException: is not a valid component Related Linksconfigure the following Splunk query to search for node logs, you can refine the search to a particular node, txid, worker, etc: instance=<instance_name_prod> sourcetype=appnode_localhost_log "Search" | sort_time