The Teams Workflow app lets you automate repetitive tasks without leaving Teams. On Teams for the web, the app often fails to run a flow, showing a generic error or a spinning icon that never completes. This happens because the web client blocks certain Power Automate connectors and background triggers. In this article, you will learn the exact causes and the step-by-step fixes to get your flows running in the browser.
You will also learn how to switch to the desktop app when the web version cannot handle a specific connector. Finally, you will see how to check your flow’s run history and adjust your browser settings to avoid common failures.
Key Takeaways: Fix Teams Workflow App Failures on the Web
- Teams admin center > Teams apps > Manage apps > Workflow: Shows the app’s permission settings and whether it is blocked for web users.
- Power Automate > My flows > Run history: Displays the exact error message and the failed step for any flow run.
- Browser settings > Cookies and site data: Clearing these fixes the “flow cannot run” error caused by stale authentication tokens.
Why the Teams Workflow App Cannot Run a Flow on Teams for the Web
The Teams Workflow app runs on Power Automate, Microsoft’s cloud automation service. When you create a flow inside Teams, the app sends a request to the Power Automate backend. On Teams for the web, the browser must handle authentication, cookies, and third-party connections. If any of these fail, the flow stops before it starts.
The most common root cause is that Teams for the web blocks third-party cookies by default in some browsers, such as Safari and Chrome with strict privacy settings. Power Automate uses these cookies to keep your session alive. Without them, the flow cannot authenticate and returns an error like “Unable to run flow” or “Something went wrong.”
Another cause is that the flow uses a premium connector, for example SQL Server or a custom API, which requires a Power Automate license. The web version of Teams does not always show the license prompt, so the flow silently fails. Finally, some flows are triggered by an event that the web client does not support, such as a file creation in OneDrive. The web app only supports manual triggers or simple scheduled triggers.
How the Web Client Differs from the Desktop App
The Teams desktop app runs on Windows or macOS and has a full Power Automate integration. It can handle all connector types and does not depend on browser cookies. The web client is a lighter version and intentionally limits some features to reduce browser load. Microsoft documents these limitations, but the error messages rarely explain them.
Steps to Diagnose and Fix the Workflow App on Teams for the Web
- Check the flow’s run history
Go to the Teams Workflow app and open your flow. Select “Run history” from the flow details page. Look for the most recent run. Click it to see the error message. If the error says “Invalid connection” or “Authentication failed,” the problem is your credentials. If it says “Premium connector required,” you need a license. - Clear browser cookies and site data
In your browser, open the settings menu. Find “Privacy and security” and then “Clear browsing data.” Select “Cookies and other site data” and click “Clear now.” Close all Teams tabs and reopen Teams for the web. Sign in again and try the flow. This fixes most authentication errors. - Allow third-party cookies for Teams and Power Automate
In Chrome, go to Settings > Privacy and security > Third-party cookies. Add “teams.microsoft.com” and “flow.microsoft.com” to the “Always can use cookies” list. In Safari, go to Preferences > Privacy and uncheck “Block all cookies.” In Edge, go to Settings > Cookies and site permissions > Manage and delete cookies and site data, then add the same sites to the “Allow” list. - Switch to the Teams desktop app
If the flow still fails, install the Teams desktop app from the Microsoft 365 portal. Sign in with the same account and open the Workflow app. Run the flow there. The desktop app handles connectors and authentication more reliably than the web client. - Check your Power Automate license
Open the Power Automate portal at make.powerautomate.com. Go to “Billing” and then “Licenses.” Confirm that your user account has a license that includes the connectors your flow uses. If not, request a license from your admin or change the flow to use standard connectors. - Recreate the flow from the web client
Delete the flow from the Workflow app and create it again directly in Power Automate. In Teams for the web, open the Workflow app and select “Create.” Choose a template that uses only manual triggers and standard connectors. This avoids the limitations of the web client.
If Teams Still Has Issues After the Main Fix
Teams Shows “Flow Cannot Run” When Using a File Trigger
The web client cannot monitor file creation events in OneDrive or SharePoint. If your flow starts with “When a file is created,” it will never trigger on the web. Use a manual trigger instead, such as “For a selected message” or “Manually trigger a flow.” Or run the flow from the desktop app where file triggers work.
Teams Workflow App Does Not Appear in the Left Navigation
If the Workflow app is missing, your Teams admin may have blocked it. Ask your admin to check Teams admin center > Teams apps > Manage apps. Search for “Workflow” and ensure the status is “Allowed.” Also check the app permission policy assigned to your user.
Flow Runs but Takes Too Long on the Web
The web client limits the timeout for flow runs to 30 seconds. If your flow runs longer, it fails with a timeout error. Split the flow into smaller steps or use the desktop app, which allows a longer timeout. You can also increase the timeout in the flow settings in Power Automate.
Teams Workflow on Web vs Desktop: Key Differences
| Item | Teams for the Web | Teams Desktop App |
|---|---|---|
| Connector support | Standard connectors only | All connectors, including premium |
| File triggers | Not supported | Supported |
| Authentication | Depends on browser cookies | Uses Windows or macOS credential store |
| Flow run timeout | 30 seconds | Up to 30 days for long-running flows |
| Best for | Quick manual tasks | Complex automation and file monitoring |
The table shows that the desktop app is the reliable choice for any flow that uses premium connectors or file triggers. Use the web client only for simple manual flows that complete in under 30 seconds.
Now you can diagnose and fix the Teams Workflow app on Teams for the web. Start by clearing your browser cookies and checking the flow’s run history. If the problem persists, switch to the Teams desktop app or adjust your browser’s cookie settings. For a permanent solution, create your flows in Power Automate and use the desktop app for all automation tasks. This approach avoids the web client’s limitations and keeps your workflows running smoothly.