Teams Approvals "Something Went Wrong. Wait a bit, then try again"

Because the failure affects multiple users, returns after successful approvals, and persists after cache clearing and reinstalling, check tenant-specific service health and open a Microsoft support request with logs captured during an actual failure rather than repeating client repair steps.

1. Check tenant-specific service health

Use an account with the Service Support admin, Helpdesk admin, or another applicable administrator role:

1. Open Microsoft 365 admin center → Health → Service health.
2. Review:
   • Issues for your organization to act on
   • Active issues Microsoft is working on
   • Issue history for the preceding 30 days
3. Check entries involving Microsoft Teams, Power Automate, Power Apps, or Microsoft Dataverse.
4. If no matching event appears, select Report an issue and provide the exact failure times and affected-user count. Microsoft can compare the report with telemetry from other tenants.^1^

Also check Power Platform admin center → Home → Service health, because Teams Approvals uses Power Automate infrastructure and stores approvals created in Teams in the organization’s default Dataverse environment.^2^ ^3^

The public status page does not provide the same tenant-specific view.

2. Capture diagnostics while the error is present

Do this immediately when Approvals starts failing—before reloading it for several minutes.

On Windows:

1. Reproduce the error in Teams → Approvals.
2. Select the Teams icon in the system tray and choose Collect support files, or press: Ctrl+Alt+Shift+1
3. Wait until the Downloading web logs banner disappears.
4. Retrieve the generated files from Downloads. The support-log package must be compressed before upload; the Prod-Weblogs package is already compressed.
5. Record:
   • Exact local date, time, and time zone
   • Affected user
   • Whether opening, creating, or responding to an approval failed
   • Approval title or ID, if available
   • Teams client version

Teams logs should be collected as soon as the problem occurs; their timestamps use UTC, so include the local-to-UTC offset in the support case.^4^

A Teams administrator can alternatively collect logs remotely:

1. Teams admin center → Users → Manage users
2. Open an affected user.
3. Select Client health.
4. Select the relevant device/client and choose Request client logs.

Remote collection supports Windows non-VDI and Mac clients and requires an eligible Teams or Global Administrator role.^5^

3. Isolate the client from the Approvals service

During the same failure window, test the affected account in the standalone Approvals web app:

1. Open Approvals.
2. Attempt the same operation.
3. Record whether:
   • Both web and desktop fail simultaneously, or
   • Only the desktop client fails.

A simultaneous failure strongly narrows the case toward the Approvals/Power Platform path rather than the installed Teams client. If only the web experience fails, capture a browser network trace after signing in and reproduce the error once; Microsoft documents browser traces as a support diagnostic for Teams web errors.^6^

4. Verify the underlying environment state

Do not change permissions speculatively. Instead, have a Power Platform administrator inspect the default environment, because all native Teams approvals are currently created there.^7^

In Power Platform admin center → Environments → Default environment, verify:

1. The environment is Active.
2. Its Dataverse database is Ready, not Disabled or Admin-only.
3. The Approvals solutions are installed under Dynamics 365 apps.
4. The required enterprise applications—Microsoft Flow Service, Microsoft Flow Dataverse Integration Service, and Dynamics CRM Online/Dataverse—are enabled.
5. Conditional Access is not blocking those applications for the affected users.

These are documented prerequisites for Power Automate Approvals; disabled or non-ready Dataverse states prevent Approvals functionality.^8^

5. Escalate with usable evidence

Open Microsoft 365 admin center → Support → Help & support and include:

• Default environment name/ID and region
• Number and scope of affected users
• Exact timestamps and time zones for several failures
• Screenshots and precise reproduction steps
• Result of desktop-versus-web testing
• Teams client versions and operating systems
• Collected Teams/web logs
• Any correlation or request IDs visible in logs or network traces
• Confirmation that cache clearing and complete reinstall were already performed and only helped temporarily
• Relevant Service health incident/report ID

Environment, region, user, run/correlation identifiers, browser, and operating-system information help Microsoft locate the corresponding backend telemetry.^9^

References

1. How to check Microsoft 365 service health
2. How do I check my online service health?
3. Manage the Approvals app in Microsoft Teams
4. Collect Teams client diagnostic logs for Microsoft support
5. Diagnostic logs for Teams Client
6. Browser logs and tracing for Teams
7. Approvals in Microsoft Teams
8. Power Automate Approvals Dataverse provisioning errors and recommendations
9. Create an effective Power Automate support request