'ActionTest' action in Flow Designer is in 'in progress' state for a very long time (days) intermittently. Issue ActionTest' action in Flow Designer is in 'in progress' state for a very long time (days) intermittently. We can see that in the working scenario, the MidServer is picked up and the action is completed without any issues. However, in the Non Working scenarios, the MidServer is not being picked up and hence the action is in 'inProgress' forever. ReleaseParisCause Upon running Test in Flow Designer for "ActionTest", execution in-progress.ECC queue shows using mid.server.SANDBOX and Output state in Processing.However, the flow is configured to use MID Application which is Reference to IntegrationHub. Upon opening MID Server Application "ecc_agent_application" found the default MID Server is set to use different MID server "Automation_S" Resolution The fix is by removing the applications (ALL & Orchestrator) in mid.server.SANDBOX. Post removing the Test i Flow Designer for "ActionTest", executed successfully using correct MID server "Automation_S" Related LinksMidServer selection happens as below :https://docs.servicenow.com/bundle/paris-servicenow-platform/page/product/mid-server/concept/c_MIDServerSelector.html-> You can configure a default MID Server that an application can use if all other possible MID Servers are unavailable. You can narrow down the list of applications that are included in the definition of ALL.https://docs.servicenow.com/bundle/paris-servicenow-platform/page/product/mid-server/task/t_SpecifyMIDServerApplications.htmlHence, it is advised to use configure the Mid server as per the requirement for the specific actions to run on it.