[BUG] Scheduled transactions suddenly exceed computation limit after days of working normally #6
Description
Current Behavior
After initializing and scheduling the first transaction, scheduled transactions are being sent properly. However, after several hours of operation, transactions suddenly start hitting the computation limit (9999), which stops the processing entirely.
Expected Behavior
Scheduled transactions should continue processing consistently over extended periods without hitting the computation limit (9999). The system should either:
- Maintain stable computation costs - Each scheduled transaction should consume a predictable amount of computation that stays well below the 9999 limit, regardless of how long the system has been running.
- Process indefinitely - Once initialized, the scheduled transaction mechanism should continue operating without manual intervention or restarts.
What are you currently working on that this is blocking?
FlowYieldVautsEVM integration. Those scheduled transactions process requests made from EVM into Cadence (where the protocol actually lives).