-
Notifications
You must be signed in to change notification settings - Fork 18
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
The application did not respond #20
Comments
Please try now |
Works, though right now the queuebot is not responding |
Fixed. |
Hey this is happening again and has been off and on happening for the past day |
Thanks for the feedback. I'm aware of the issue. I updated a bunch of the libraries, NodeJS, and OS dependencies on Friday. One of those changes added a memory leak. I haven't been able to figure out which one, but I'm working on it when I have free time. Hopefully I will get it fixed tomorrow. Sorry for the inconvenience! |
Whenever I pull someone from a queue using /next, the user is notified but an error message "The application did not respond" appears.
The text was updated successfully, but these errors were encountered: