Approval state is requested eventhought the change request state changed to new and flow is cancelled.Issue When a change is reverted back to new from assess, the approvals did not move to no longer required and instead stay in requested state. The flow 'Change - Normal - Assess' is cancelled instead of completed.ReleaseAnyCauseAs the flow is running in foreground, it impacted the user transaction. User clicked on cancel in the pop-up that comes as "Running Transaction". Below are the log snippet, WARNING *** WARNING *** Transaction cancelled: cancelled by user requestCaused by: com.glide.db.TransactionSQLCancelledException: cancelled by user requestResolutionChange the flow designer's when to run condition to 'run flow in background' to avoid the behavior. This will prevent the flow from running in the foreground and causing the user-initiated cancellation and incomplete approval state transition.