OG
CCConvex Community
•Created by OG on 2/2/2024 in #support-community
synchronizes issue
The issue we are currently facing is that there's a feature in my business that synchronizes the balance, and this script runs every 15 seconds. When I execute it, I need a parameter, the starting block number.
If the script doesn't finish within 15 seconds, in reality, another task is initiated. The effect of this task is actually the same as the previous one, but when recording the amount, the situation of having the same txhash occurs, which essentially wastes the resources of one execution.
I can add a field in the table to judge this, but this also occupies the read and write of the table.
I hope there could be a system-level variable that lets me distinguish whether this task is currently in execution.
Alternatively, is it possible to create a type for the cron? For instance, if it is an exclusive cron, then it does not allow concurrent execution.
3 replies
CCConvex Community
•Created by OG on 2/1/2024 in #support-community
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?
14 replies