Hi everyone, I’m Steve, a product manager here at Bubble focused on helping you scale your apps. I’m excited to share that the Schedule API Workflow on a List action can now schedule up to 100K workflows, making this a robust, native option for completing bulk operations . This update builds on prev…

Hi Sarah, The interval you set is respected by Bubble, even as low as zero (see docs ). There is no inherent problem with scheduling workflows that contain many actions. It may take longer for all of them to be completed, but the scheduling and execution will support this without issue.

Hi Eli, Yes, Bubble has logic in place for Dedicated instances to throttle the execution of the workflows if needed to ensure they run successfully and your app remains functional. The scheduling is controlled by you, as you set the start time and interval. However, in cases where your app is thro…

@steven.harrington I encoutered this probleme and report it to bubble support, so yes it happen that the interval is not respected

[image] ambroisedlg: However I’m still having trouble understanding how such a basic workflow can fail from a logical standpoint. I think that Bubble just has not taken the time to setup the code structure so as to handle this for us correctly. If step 2 is referring to an object from step 1,…

Okay, so is that something like this below? On backend workflow have two of the parameters be of the same type. [Screen Shot 2024-04-10 at 12.08.27 AM] Then on any action within that backend workflow that I want to run when the list has finished processing I use the condition like below [Screen…

I’ve tried it how you had it above and for some reason it sometimes will fail. I always have the “last item” field a yes/no field and then have it be “list:last item is this item” in the field when scheduling. Then trigger your action based on the last item field being “yes”. That has worked well …

[image] aj11: I always have the “last item” field a yes/no field That will also reduce the WU consumption, in addition to your use case of ensuring it doesn’t fail. Thanks for the details. Sounds like a must use approach with the schedule on a list, especially now that the ‘race conditions’ …

I think it’s fine the way it is. The mitigation path is there just by putting an interval in for 2,3,5 seconds etc. Keep in mind, even with the “last item” approach, there is no guarantee that the last item actually runs last if Bubble is trying to run all at once. All it really does is guarantee y…

[image] steven.harrington: We are now actively exploring and planning new ways to enable bulk data updates specifically, which will likely be more in line with the method you are describing. More to come later this year! Thanks @steven.harrington that is great news!

[Feature Enhancement] Schedule 100k Workflows with Schedule API Workflow on a List

Announcements New features

lottemint.md June 10, 2024, 6:32pm 61

@steven.harrington

“good” updates, thx

Topic		Replies	Views
[Feature Enhancement] Improved Scalability of Schedule API Workflow on a List New features	42	9390	May 1, 2024
Schedule API Workflow on List - failing for lists of 100+ items? APIs	20	6320	July 7, 2022
Schedule API workflow on a list - does the list have a limit? Questions	23	9360	August 5, 2021
Backend workflows failing APIs	6	503	April 4, 2024
Why does scheduling an API workflow on a list take so long? Database	23	2830	April 15, 2021

[Feature Enhancement] Schedule 100k Workflows with Schedule API Workflow on a List

Related topics