We just updated from a legacy plan to the new plans. We have found on several “Schedule as a list” actions that if we leave the interval blank (recommended setting), the full list does not get processed, even with as few as 3-5 items in the list. As soon as we space it out by, say 1 second, then the list runs. And we’ve even found that it happens faster than 1 second.
We have filed a bug report, and have checked that there is nothing in the scheduled actions that could change the actual source list (since that would obviously break things being created at the same time) but curious if others are experiencing this?
Having to find all the scheduled on a list processes is going to be super time consuming, and we think the great benefit of the new rates is being able to have up to 100k things scheduled at the same time since capacity is no longer a limit. In this way bulk operations don’t take forever like in the recursive wfs we used to need to do…
This issue is a race condition related issue rather than timeouts. On legacy, workflows generally run at 1 per second. On WU plans, you can get about 50 per second depending on the size of the workflow.
100,000 works fine for me. However, if running in a BEWF, the BEWF has a 5 minute timeout and it does still take time to schedule.
Thanks all. Does seem to be a race condition. I suppose if bubble were to update the ADD to a list so something is actually added and the whole list is not changed int eh background, that would solve the issue. Shame that has not been implemented but I guess it’s likely not taht easy to do.
Painstakingly going through every workflow 1 by 1 to see fi we schedule it on a list, and if we do can we run it without interval. I wish there was an easier way to search… This is going to take hours.
