question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

http 500 errors on connector service (bots not able to respond to users)

See original GitHub issue

Folks, we are seeing service deterioration for all our slack and SFB bots starting about 30 minutes ago. Any known outages you are aware of?

Users conversing with our bots are not able to get back responses because the bot response to the SDK is failing with 500 errors.

This is across multiple bot framework accounts.

Error: Request to 'https://state.botframework.com/v3/botstate/slack/conversations/B4*****9/users/U4*****9' 
failed [500] Internal Server Error
Request._callback (/****/node_modules/botbuilder/lib/bots/ChatConnector.js:542:46)

Bot Info

  • SDK Platform: node js
  • SDK Version: 3.11.x
  • Active Channels: SFB, Slack
  • Deployment Environment: Non Azure Bot Service (hosted externally)

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
EricDahlvangcommented, Jan 18, 2018

This was a temporary issue with the Default State Service. This service is being deprecated: https://blog.botframework.com/2017/12/19/bot-state-service-will-soon-retired-march-31st-2018/

Bots that already have implemented a custom state client did not experience the problem. Please add a custom state client to your bots.


@v46 Bot Framework does not currently have a status page.

0reactions
v46commented, Jan 18, 2018

Thank you @EricDahlvang

Read more comments on GitHub >

github_iconTop Results From Across the Web

http 500 errors on connector service (bots not able to respond ...
Folks, we are seeing service deterioration for all our slack and SFB bots starting about 30 minutes ago. Any known outages you are...
Read more >
What Is a 500 Error & How to Fix It | Sucuri Blog
1. This is a good troubleshooting step. This is done before looking for more debugging on your site to confirm that the issue...
Read more >
Troubleshoot HTTP 500 Internal Service Errors with Azure Bot ...
The first step in troubleshooting 500 errors is enabling Application Insights. For AppInsights samples, see the luis-with-appinsights C# sample ...
Read more >
500 error: how to solve - SupportHost
The 500 error is a server error and occurs when the requested address cannot be reached. Let's see what it depends on and...
Read more >
A Guide to HTTP 500 Server Error Codes - Blue Frontier
Perhaps the most common message encountered, this indicates a generic server error that's displayed when the server cannot determine the exact problem. 501...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found