Graceful Shutdown - Flow DesignerBackground of prior to Utah when there was a node shutdown or restart, a flow would just terminate abruptly, and it would be stuck with in-progress state. Tokyo release has a feature implemented to identify this situation and mark those full contexts as presumed interrupted. More information is here KB1122093 Starting from Utah Node Shutdown/restart process would be done in two steps usually for allowing system to shutdown gracefully. Step#1: Prepare for Shutdown This indicates that the node is about to shut down, and system should start preparing for shutdown. Node stops processing any new background flow executions.System attempts to pause any in-progress flow executions so that they can resume on another node. System would not pause the flow execution in below conditions and they might be abruptly terminated if there is not enough time to complete the execution. System attempts to pause flows only between actions executions. Not leaving any actions incomplete.DataStream involved flows won't get paused.Any Foreground executions are not paused. Quick API calls are not paused. State of the flow will become paused until it resumes again. There is an event "RESUME_FLOW_MESSAGE" created to resume this flow execution on another node.System safely pauses the flow executions after step#1 (Prepare for Shutdown) untill step#2(Shutdown) and Flow logs are available to confirm the same.INFO log "Flow execution paused due to node shutdown." is available under sys_flow_context Step#2 Shutdown indicates that the node is being shutdown. Cancellation Event is scheduled with default 10 min to cancel any flows that are still in progress. Giving 10 min time for flows to be processed on another node before cancelling.Cancellation schedule time can be configured by property "com.glide.shutdown.schedule_flow_cancellation_after_sec"Event can be identified by name "flow.cancel_due_to_shutdown"INFO log "Flow shutdown handler initiated, sys_flow_context count <count> which are in progress" is available to identify if FlowShutdownHandler called to schedule cancellation. If there is an unplanned shutdown/restart ( ex: power outage ), System would not have time to save the flow plan or any of the execution details. which leads flow going into PRESUMED_INTERRUPTED (KB1122093).