I don’t know what your situation is atm, but Bubble support couldn’t help us with our bug report.
Regarding the Bubble Scheduler
I’ve analyzed the issue.
They indeed enhanced the Scheduler, but didn’t test it well as I see.
It works well if the scheduled workflow contains synchronous actions only.
If the scheduled workflow contains such actions as scheduling (asynchronous) other workflows - when we have a problem.
So, the update ([Feature Enhancement] Schedule 100k Workflows with Schedule API Workflow on a List) is good for simple scheduled workflows. But the update downgraded the speed and performance for scheduled workflows that schedule other ones.
The issue is that when you schedule an API workflow on a list (even if the list contains 1000 items) and leave the interval field empty, the system tries to process the list as quickly as possible and execute all actions within the workflow. If there are steps inside the workflow, such as scheduling another API workflow with a scheduled time of the, for instance, current date/time, the system cannot properly assess how to schedule these actions correctly. At the time of scheduling the workflow (Schedule on a List > Schedule API Workflow), the system cannot account for the queue that is being created simultaneously.
What confuses me:
Honestly, I think the examples attached on the photo are not actual.
Such apps as Hiring Marketplace have tons of scheduled complex workflows (synchronous, asynchronous, etc.).
Our client’s app’s monthly WU usage is kinda 11M.
We got a delay of a couple of hours while the WU usage for this short period was 350K.
Since Bubble support wasn’t able to assist, I’ve figured out a quick solution.
Instead of just Current date/time:
The idea is adding a dynamic delay. In my case, I’m generating a random number from 1 until 9.
It doesn’t throttle the Scheduler since each workflow (Schedule on a List > Schedule API Workflow) schedules at different time.
@nic3
please let me know if that helps