Microsoft Teams — Troubleshooting

Troubleshoot common Microsoft Teams integration errors and choose the next action.

📘

Related setup guide

Setting up Microsoft Teams? See the Microsoft Teams integration setup guide.

Use this page to troubleshoot common Microsoft Teams integration errors and choose the next action.

Error messageLikely meaningRecommended next steps
WorkflowTriggerIsNotEnabled","message":"Could not execute workflow trigger 'manual' with state 'Suspended': trigger is not enabledWorkflowTriggerIsNotEnabled (trigger suspended)

The workflow is turned off. Ask the Teams or Power Automate admin to turn it on.

If the workflow was recreated, update the integration with the new workflow link. Then reconnect the integration and try again.

Power Automate emails you: "Alert: Your operation has been throttled"This comes from Microsoft, not from Xyte. Your workflows sent more requests than Microsoft allows in a short time. Microsoft counts these limits per account and Teams connection, so many workflows owned by the same person share one limit. While a flow is throttled, its posts can be delayed, and if it keeps happening, some posts can fail.

Open the flow's run history in Power Automate to see which step was throttled.

Have the workflows owned by a dedicated, licensed service account instead of a personal account. If it continues, ask your Microsoft admin about a Power Automate Process license for the flows.

To send fewer posts, set a minimum incident priority on the Teams integration in Xyte. See Microsoft Teams connector limits.

Webhook URL is not updatedCreate a new Teams webhook or Flow URL and paste it into the integration. Then reconnect the integration and try again.
end of file reachedThe Teams integration sent or received a malformed or truncated payload, so parsing stopped unexpectedly at the end of the input.
Failed to open TCP connection to :80 (Connection refused - connect(2) for nil port 80)The Teams integration tried to connect to an HTTP endpoint on port 80, but the host or URL was missing or incorrect, so the connection was refused.Verify the integration’s target URL, hostname, and port. Use the correct Teams webhook or API URL, typically HTTPS on port 443, and make sure outbound access is allowed.
{"error":{"code":"DirectApiAuthorizationRequired","message":"The OAuth authorization scheme is required. Please add authentication scheme and try again."}}The Teams or Power Automate endpoint is protected by OAuth, but the integration is calling it as a webhook without an OAuth bearer token.

In the flow trigger, set Who can trigger the flow to Anyone. Save the flow, copy the new URL, update the integration, and try again.

Microsoft's guide

DirectApiAuthorizationRequired keeps coming back after you updated the integration with a new linkA space still has its own Teams link from before the change. Spaces can override the integration's link under Incident routing, and an alert from that space is still sent to the old link. When it fails, the whole Teams integration is disabled, so alerts from every space stop.Open the spaces that have their own Microsoft Teams link (space settings → Incident routing → Microsoft Teams). Replace the link with the new one (it contains sig=), or remove it so the space uses the integration's link. Then reconnect the integration and send a test incident from one of those spaces.

Did this page help you?