Fix Teams Workflow App Cannot Run a Flow in a New Teams Client

You open the Workflow app in the new Teams client, select a template, and click Next, but the flow never starts. The app may show a blank screen, an error about permissions, or a message that the flow was not created. This problem usually comes from a missing connection to Power Automate or from an outdated Teams app cache. This article explains the exact causes and gives you step-by-step fixes to get your flow running again in the new Teams client.

The new Teams client uses a different framework than the classic client, which changes how the Workflow app loads and connects to Power Automate. Many users see this issue after switching to the new client because the app permissions or the local cache are not carried over. You will learn how to verify your admin policies, repair the app, and rebuild the connection so your flows work in both clients.

Why the Workflow App Fails to Run a Flow in the New Teams Client

The Workflow app in Teams is a wrapper that connects to Power Automate. When you select a template, the app sends a request to create a flow in your default environment. If that request fails, you see an error or nothing happens. The root cause is usually one of three things: the Workflow app is not enabled in your Teams admin policies, your user does not have the right permissions in Power Automate, or the app cache is corrupted.

The new Teams client loads apps differently than the classic client. It uses a more isolated runtime, which means that app data from the classic client is not automatically available. This can cause the Workflow app to appear as if it has no connection to Power Automate, even though your account is valid. Additionally, if your organization has set a custom app permission policy that does not include the Workflow app, the app will be blocked silently.

Another common cause is that the default Power Automate environment is missing or that your user is not a member of the Environment Maker role. Without this role, you cannot create new flows from templates. The Workflow app does not give you a clear error message for this case, so you may see a blank dialog or a spinning wheel.

How the New Teams Client Changes App Behavior

The new Teams client is built on a web-based framework that runs apps in isolated iframes. This means that the Workflow app does not share session data with the classic client. When you switch to the new client, you may need to re-authenticate the app or re-approve its permissions. If the app was previously installed in the classic client, the new client may not detect that installation, showing the app as available but not properly connected.

Steps to Fix the Workflow App in the New Teams Client

Follow these steps in order. The first step checks your admin policy, the second clears the app cache, and the third tests your Power Automate connection. Complete all steps before contacting support.

1. Verify the Workflow app is allowed in your Teams admin center
   Sign in to the Teams admin center at admin.teams.microsoft.com. Go to Teams apps > Manage apps. Search for Workflow. Confirm that the app status is Allowed. If it shows Blocked, click the app, then select Allow. Also check your app permission policy under Teams apps > Permission policies. Ensure that the policy assigned to you includes the Workflow app.
2. Reset the Workflow app in the new Teams client
   Open the new Teams client. Click your profile picture at the top right, then select Settings. Go to Apps and click Manage your apps. Find Workflow, click the three dots next to it, and select Reset. Confirm the reset. This clears the app cache and re-registers the app with the new client. Restart Teams.
3. Check your Power Automate environment and permissions
   Go to make.powerautomate.com and sign in with the same account. In the top right, confirm that the environment shown is your default environment. If no environment is listed, click the environment selector and choose Default. Then go to Solutions and check if you can create a solution. If you cannot, ask your admin to assign you the Environment Maker role in the Power Automate admin center.
4. Create a test flow directly in Power Automate
   In Power Automate, click Create and choose a simple template, for example Send a message to Teams. Fill in the required fields and click Create flow. If this succeeds, the issue is specific to the Teams app. If it fails, your Power Automate account has a permission problem that must be fixed first.
5. Reinstall the Workflow app in Teams
   In the new Teams client, go to Apps and search for Workflow. Click the app, then select Add or Install. If it is already installed, click the three dots and choose Uninstall, then add it again. This forces a fresh installation with the correct permissions.
6. Switch to the classic Teams client temporarily
   If the issue persists, test the same flow in the classic Teams client. Click your profile picture, then select Switch to classic Teams. Open the Workflow app and try to create the same flow. If it works there, the problem is isolated to the new client. You can continue using the classic client while you wait for a fix, or you can try the next step.
7. Clear the Teams cache completely
   Close Teams completely. Press Ctrl + Shift + Esc to open Task Manager and end all processes named Teams. Then press Ctrl + R to open the Run dialog. Type %appdata%\Microsoft\Teams and press Enter. Delete the contents of this folder. Restart Teams and sign in again. This removes all cached app data, including the Workflow app cache.

If the Workflow App Still Cannot Run a Flow

After completing all the steps above, if the app still fails, the problem may be related to your organization’s conditional access policies or to a known issue with the new Teams client. The following sections cover these specific situations.

Workflow App Shows a Blank Screen After Clicking Next

A blank screen usually means the app cannot reach Power Automate. This can happen if your network blocks the domain make.powerautomate.com or if the new Teams client has a proxy issue. Check your system proxy settings in Windows. Press Ctrl + I to open Windows Settings, go to Network & Internet > Proxy, and ensure that the proxy is configured correctly. Also add the following domains to your firewall allowlist: make.powerautomate.com, flow.microsoft.com, and service.powerapps.com.

Error Message: “You Don’t Have Permission to Create Flows”

This error appears when your user account is not assigned the Environment Maker role in Power Automate. Your Teams admin must assign this role. In the Power Automate admin center, go to Environments, select your default environment, then click Access. Add your account and assign the Environment Maker role. After the role is assigned, wait 10 minutes and try again in Teams.

Workflow App Works in Classic Teams but Not in New Teams

This is a known compatibility issue. The new Teams client uses a different authentication flow for third-party apps like Workflow. To work around it, you can pin the Workflow app to your left rail in the new client and then sign out and sign back in. Click your profile picture, select Sign out, then sign in again. This refreshes the token for the app. If the issue continues, use the classic client until the next Teams update.

New Teams Client vs Classic Teams Client for the Workflow App

The table below compares how the Workflow app behaves in each client. Use this to decide which client to use while you troubleshoot.

Item	New Teams Client	Classic Teams Client
App loading speed	Faster, but can show blank screens if cache is corrupted	Slower, but more stable for legacy apps
Authentication to Power Automate	Uses a new token flow that may fail if the app is not reset	Uses the same token as the Teams client, so it works reliably
Cache management	Requires manual reset of the app in Settings	Cache is shared with the system, so clearing Teams cache is enough
Compatibility with Workflow templates	Most templates work after proper setup	All templates work without extra steps

Now you know how to fix the Workflow app in the new Teams client by checking your admin policies, resetting the app, and verifying your Power Automate permissions. Start by resetting the Workflow app in Teams Settings, as that solves the issue for most users. Then verify your Environment Maker role in Power Automate if the reset does not help. For persistent problems, use the classic client while you wait for the next Teams update.

To avoid this issue in the future, always test new flows in Power Automate first, then add them to Teams. You can also pin the Workflow app to your left rail and sign out and back in after a Teams update. If you manage multiple users, assign the Environment Maker role in the Power Automate admin center before rolling out the new client.