Closed macieyng closed 7 months ago
@macieyng Thanks for your feedback! We will investigate and update as appropriate.
@macieyng Thank you for your feedback! I recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds. [Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows. [Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1) Thank you for your time and patience throughout this issue.
Hi, I'm not sure to whom I should report this, so redirect me there if that's a wrong place.
I'm having an issue with some requests. I was testing if I get the same results with identical input and it turned out that I wasn't able to confirm that due to the fact that I often get 500 responses saying as much as
{"error":{"code":"InternalServerError","message":"Internal server error"}}
. I guess there could be an issue in your backend. Basically sometimes it's 200, but often it's 500. Via Portal I learned that I'm not hitting the rate limit.Additional question: is there a release page for Stiching API? Which version should be used? Response header includes a few of them. It seems like the recent one is 2024-02-01. Should I use this one instead? That's a bit confusing...
Request data (REDACTED):
Sent to
Response headers
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.