disconnect
Background of the incident: Within Convex, we have set up two projects, named Axon and Axon-dev. Axon is used for the official runtime environment, while Axon-dev is for internal testing purposes. The issue arose when the code for Axon and Axon-dev was completely identical, yet two different phenomena occurred.
Phenomena observed: At the time, there were over 10 users using the system, including 2 of our testers. These testers simply logged into the website and did not perform any actions. However, the page would suddenly crash. Upon opening the browser console, an error was observed: the connection to the Convex service was interrupted. Meanwhile, the testers also accessed Axon-dev without encountering the same issue.
Subsequently, developers started to check the logs in Convex for troubleshooting and discovered the following errors in the Axon project, while the Axon-dev project did not exhibit any
Regarding the official response and proposed solution: We were advised to reduce the use of complex algorithms in our queries and mutations. We will try our best to address this. However, we still want to understand the current issue's cause. Why is it that the testers, without any operations, would get disconnected from Convex, while some users can maintain normal communication despite frequent operations?
13 Replies
Hey @OG! Want to let you know that we're looking into this, and we have an idea of what's going on. I'll have a more detailed response later today (and also respond to your support email with any information more specific to your situation)
Hi @OG . We rolled out an improvement yesterday afternoon that should significantly reduce the number of timeouts you're seeing. If you're still seeing errors today, can you post or dm me the errors you're seeing and a screenshot of either or both of the browser console and the Convex dashboard? I'd be happy to investigate further.
Thanks for the reply. I believe your web socket and application are crashing due to errors thrown by your Queries and Mutations. In this example
As for the other errors - Do you use other web sockets or libraries that use web sockets in your application? I believe
getListByAxonAndUserOrderByDesc Server Error is caused by an Error thrown by your axon_chat:getListByAxonAndUserOrderByDesc Query function. Errors thrown by your code inside of your Queries and Mutations will crash the Convex web socket and client. The error message is obfuscated to Server Error because your browser is talking to your production instance. To see non-obfuscated errors for your production instance, go to the Logs page in your Convex dashboard. I've also noticed that the error rate for your Queries and Mutations is generally high. Would you like to set up time to talk about these errors in more detail?As for the other errors - Do you use other web sockets or libraries that use web sockets in your application? I believe
Authorization error: Unauthorized: origin not allowed is not coming from Convex.Thanks for the reply！ I'd like to set up time to talk about these errors in more detail . could you send me the link of your Calendly?
Hi, here's a link: https://calendly.com/convex-sam/30min. That second set of errors looks similar to the first. You'll see more detail in the Logs page on your dashboard at https://dashboard.convex.dev/
Convex Dashboard
Manage your Convex apps
@OG have you chatted with Sam yet about it? And are you sure that is the Convex websocket? None of those stack traces have functions I recognize
yes, i am sure this is Convex WebSocket our users still got connection error
The bottom error looks like Convex (check the logs view on the convex dashboard for why getAttributesByAxon is throwing an error) but the top two errors shown here don't look related to Convex. They look like React Native errors similar to https://github.com/WalletConnect/walletconnect-monorepo/issues/2934
GitHub
WalletConnectV2 ReactNative => Authorization error: Unauthorized: o...
Describe the bug I integrated WalletConnect V2 with ReactNative using WalletConnectModal but for some reason when the app starts I see loads of WebSocket errors in the console. {"context"...