botframework-sdk: [Performance] Refresh Access Token Failed with Status code: 400
System Information (Required)
- SDK Language: NODE
- SDK Version: 3.7.0
- Development Environment: LOCALHOST, AZURE_APP_SERVICE
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.
2017-07-25T18:25:04.264999000Z Error: Refresh access token failed with status code: 400
2017-07-25T18:25:04.265192000Z at Request._callback (/usr/src/app/node_modules/botbuilder/lib/bots/ChatConnector.js:489:28)
2017-07-25T18:25:04.265351000Z at Request.self.callback (/usr/src/app/node_modules/request/request.js:187:22)
2017-07-25T18:25:04.265478000Z at emitTwo (events.js:106:13)
2017-07-25T18:25:04.265627000Z at Request.emit (events.js:194:7)
2017-07-25T18:25:04.265760000Z at Request.<anonymous> (/usr/src/app/node_modules/request/request.js:1044:10)
2017-07-25T18:25:04.265870000Z at emitOne (events.js:96:13)
2017-07-25T18:25:04.266006000Z at Request.emit (events.js:191:7)
2017-07-25T18:25:04.266130000Z at IncomingMessage.<anonymous> (/usr/src/app/node_modules/request/request.js:965:12)
2017-07-25T18:25:04.266257000Z at emitNone (events.js:91:20)
2017-07-25T18:25:04.266393000Z at IncomingMessage.emit (events.js:188:7)
2017-07-25T18:25:04.266521000Z at endReadableNT (_stream_readable.js:975:12)
2017-07-25T18:25:04.266649000Z at _combinedTickCallback (internal/process/next_tick.js:80:11)
2017-07-25T18:25:04.266826000Z at process._tickDomainCallback (internal/process/next_tick.js:128:9)2017-07-25T18:25:04.264999000Z Error: Refresh access token failed with status code: 400
2017-07-25T18:25:04.265192000Z at Request._callback (/usr/src/app/node_modules/botbuilder/lib/bots/ChatConnector.js:489:28)
2017-07-25T18:25:04.265351000Z at Request.self.callback (/usr/src/app/node_modules/request/request.js:187:22)
2017-07-25T18:25:04.265478000Z at emitTwo (events.js:106:13)
2017-07-25T18:25:04.265627000Z at Request.emit (events.js:194:7)
2017-07-25T18:25:04.265760000Z at Request.<anonymous> (/usr/src/app/node_modules/request/request.js:1044:10)
2017-07-25T18:25:04.265870000Z at emitOne (events.js:96:13)
2017-07-25T18:25:04.266006000Z at Request.emit (events.js:191:7)
2017-07-25T18:25:04.266130000Z at IncomingMessage.<anonymous> (/usr/src/app/node_modules/request/request.js:965:12)
2017-07-25T18:25:04.266257000Z at emitNone (events.js:91:20)
2017-07-25T18:25:04.266393000Z at IncomingMessage.emit (events.js:188:7)
2017-07-25T18:25:04.266521000Z at endReadableNT (_stream_readable.js:975:12)
2017-07-25T18:25:04.266649000Z at _combinedTickCallback (internal/process/next_tick.js:80:11)
2017-07-25T18:25:04.266826000Z at process._tickDomainCallback (internal/process/next_tick.js:128:9)
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 1
- Comments: 22 (2 by maintainers)
@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.
The incident has been resolved, bots should be back to normal activity now.
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?