-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Performance] Refresh Access Token Failed with Status code: 400 #3196
Comments
@sharmadine Thanks for reporting. We are experiencing a service interruption and we've got multiple engineers looking into it. Will update you when we have more details. |
Hi @nwhitmont Same here |
Also having the issue. |
+1, for myself and my clients. |
+1 Let us know when it is fixed |
+1, arg |
+1 bot is on mute |
+1 |
3 similar comments
+1 |
+1 |
+1 |
plus one |
same here |
We all know that it is still in Preview, but, for those who have their Bots under BotFramework infraestructure... how do you explain this downtime to your customers? |
same |
+1 |
I seem to have improved |
The incident has been resolved, bots should be back to normal activity now. |
Yes, the bot is alive again... thanks. |
my bot is still not replying? |
I apologize, I just found the issue. It made me get confused since the issue appeared along this one and was impossible for me to debug. So, I changed the namespace and project name of my bot application. Apparently this made Azure app service believe there were multiple API controller endpoints somehow. And that's why the Bot Framework connector couldn't reach my bot application. Sorry for the inconveniences! |
System Information (Required)
Issue Description
Our Production Bot is deployed and configured for FB, Slack, Skype, Web. It was working perfectly well across channels. There's no new code / release to the prod env.
Since 30 mins, the bot is down with errors in log files - refresh access token issue.
Please find the log entries below.
I am not sure what's the issue. The Bot just stopped working, which seems some issues with Token Issue / Refresh API Endpoints.
The text was updated successfully, but these errors were encountered: