You’re offline. This is a read only version of the page.
I have a team with 144 channels in it. If I use the Power Automate List Channels action, I get this response:
Share
Report
2,337{
"error": {
"code": 504,
"source": "australia-001.azure-apim.net",
"clientRequestId": "dbe71eb0-0b74-4e3a-9f00-debba7e54fa8",
"message": "BadGateway",
"innerError": {
"error": {
"code": "UnknownError",
"message": "",
"innerError": {
"date": "2020-11-26T22:54:47",
"request-id": "c7481058-b283-4dae-94e5-29f1cefffc22",
"client-request-id": "c7481058-b283-4dae-94e5-29f1cefffc22"
}
}
}
}
}I get the same issue using the MicrosoftTeams.GetChannelsForGroup() function in Power Apps when the same 144 channel team is used. Other teams with fewer channels are fine.
I looked up the documentation both for the Power Platform/Logic Apps connectors and also the Graph API List Channels endpoint and there's no mention of a limit.
I can successfully list all the channels using this Graph API endpoint: https://graph.microsoft.com/v1.0/teams/{team-id}/channels but the response takes approximately 30,000 ms. The problem is with the Power Platform/Logic Apps connector rather than the underlying API.
Is there a limit to the number of channels or a response timeout in the connector that isn't documented?
Hi @WillPage,
I think it is not the issue about the limitation of list channel number, cause I tested the List channels action on my side to get 150 channels in a team, not found the same issue. You could also use Flow to create 150 simple channels to test it.
I can see that the error report is 504 error, it is a BadGateway error, so you could check the gateway if works correctly, you could also recreate a new one to test it.
Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
All responses (
Answers (
