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
We just migrated to the heroku-16 stack and with that upgraded to Workless 2(.2.0). However, once deployed to Heroku, our whole web app comes to a grinding halt after a few minutes with a "Excon::Error::TooManyRequests" exception. Judging from the stack trace, it seems that Workless accesses the Heroku API with every web request that comes in. Since we have a relatively high traffic app (many mico transactions), the API seems to run over its rate limit.
This has never been a problem with version 1 of Workless. Any way to get this working again like it did before?
We just migrated to the heroku-16 stack and with that upgraded to Workless 2(.2.0). However, once deployed to Heroku, our whole web app comes to a grinding halt after a few minutes with a "Excon::Error::TooManyRequests" exception. Judging from the stack trace, it seems that Workless accesses the Heroku API with every web request that comes in. Since we have a relatively high traffic app (many mico transactions), the API seems to run over its rate limit.
This has never been a problem with version 1 of Workless. Any way to get this working again like it did before?
Here's a stack trace:
The text was updated successfully, but these errors were encountered: