9 Replies
hey seth, could you DM me your deployment name?
Thx for the report! Looking into it. Might be a bad error message or a bad error classification or also possibly an internal error.
Ideally we can make such a message is more actionable and elucidating!
Was this resolved?
I think we tracked down the root cause, but would need the deployment name to confirm.
I'm getting this again now
and lots of disconnections
and now it's fixed
are you able to see better error messages from the dashboard logs for these new errors? and just to clarify, was dusty caterpillar the same deployment you were originally seeing
Transient error while executing action in the dashboard logs for? in the previously reported case, there should be a more helpful user error message now about making sure you await your promises. i'm currently not seeing any relevant internal errors that match up to the timeline for yesterday, so my guess is that the disconnections are a different issue.Close code 1006 means the client was not able to connect to the server -- contrast with 1011 which means server internal error and 1013 which means the server is overloaded. So with 1006 there wouldn't be any error messages on our side. It could be because the network is dropping connections before they reach the server. I'll look into reproducing the issue with load testing. Sorry about the issues. Let us know if it happens again!