The delays were happening because the system load increased faster than expected after reaching 800+ holders. When activity spikes like that, the Helius API can experience higher request volume, which leads to slower response times. Since the Flywheel system is tightly integrated with Helius and the C++ backend, every update, balance check, and reward cycle depends on real-time API calls. If the number of requests grows suddenly, the queue can temporarily build up and cause small latency. After the optimization and update, the request handling has been improved, caching has been added, and the C++ processing layer now reduces unnecessary API calls. This helps the Flywheel system stay stable and run smoothly even under higher load.

the Helius API has been updated we did not expect to reach 800 holders within just 1 hour the system is now running smoothly with no delays expected