Troubleshooting Flow if it gets frozen after being triggered

Article Overview:

This article will cover how you can achieve the following:

Resolve issues where Flow might break or freeze after being triggered, ensuring it is correctly installed and executed without interruptions.

Problem Statement:

Users may encounter situations where a Flow breaks or freezes upon being triggered.
This typically happens when the Flow installation user is no longer active, such as when they’ve left the organization or their associated email ID has been deactivated. As a result, Flow fails to execute properly, causing disruptions.

Solution:

• Step 1: Identify the Flow installation user. Confirm whether the user is no longer active or if the email ID associated with the Flow account has been deactivated.
  
  
• Step 2: Reinstall the Flow app using an active user account with write access to the project. Ensure the selected user is actively involved in the project and holds the necessary permissions
  
  
• Step 3: Follow the installation guide for the Flow app, available here: Installing Flow. This guide provides detailed steps to reinstall the app correctly.
  
  
• Final Step: To avoid similar issues in the future, avoid using an employee’s personal account for installing the Flow app. Instead, consider establishing a team process to securely install apps on customer accounts. Alternatively, provide customers with instructions to install the app themselves, should they prefer.
  
  

Examples: 

• A user encountered an issue where the Flow app failed to execute because the installation was tied to the deactivated email account of a former employee. After following the steps to reinstall the app with an active account that had the correct permissions, the Flows executed successfully without further problems.