You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've used Scout in the past and loved the quick actionable insights to make improvements (n+1's, etc). I installed the heroku addon and deployed, and received thousands of H15 Idle connection errors, caused by actioncable connections. As soon as I uninstalled the gem and redeployed... no more errors.
Heroku considers these errors, so if you have the built-in "response error notification" enabled in Heroku, you will get emails forever about these H15 errors, and you will see in this graph the errors and no more errors with deploy eb7010db when I removed the scout gem.
.
The text was updated successfully, but these errors were encountered:
Thanks for the report @jeffblake - I'm surprised that we would interfere with ActionCable connections, since we don't have any instrumentation there. Can you provide some info on which rails version you're running and which Scout version was used? Was there any indication that it was happening on just one endpoint, or multiple? Happy to take a look at your Gemfile.lock if you can send it over to support@scoutapm.com as well as any logs from Heroku that you can send over showing the error and related lines.
I've used Scout in the past and loved the quick actionable insights to make improvements (n+1's, etc). I installed the heroku addon and deployed, and received thousands of H15 Idle connection errors, caused by actioncable connections. As soon as I uninstalled the gem and redeployed... no more errors.
Heroku considers these errors, so if you have the built-in "response error notification" enabled in Heroku, you will get emails forever about these H15 errors, and you will see in this graph the errors and no more errors with deploy
eb7010db
when I removed the scout gem..
The text was updated successfully, but these errors were encountered: