Schedule as a list fails without interval setting

crathbun · 2024-09-27T11:47:34.571Z

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…

ambroisedlg · 2024-09-27T12:28:08.370Z

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

@steven.harrington This update caused scheduled API workflows to not function properly and it needs to be fixed URGENTLY. I have done tests regarding the issue and I am sharing the steps for you and other forum members to test. Create 2 data types: [Screenshot 2024-03-29 at 01.04.55] Define the fields for these types as follows: Item’s Fields: [Screenshot 2024-03-29 at 01.05.00] Item Group’s Fields: [Screenshot 2024-03-29 at 01.05.05] Manually create one “Item Group” from the Data…

ZubairLK · 2024-09-27T12:29:20.776Z

Even on WU plans, timeouts do happen.

The limits are higher but not unlimited or infinity…

Are you finding any timeouts in the logs?

Thanks
Zubair

georgecollier · 2024-09-27T16:36:05.762Z

ZubairLK:

Are you finding any timeouts in the logs?

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.

crathbun · 2024-09-27T18:38:08.205Z

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.

image499×673 36.2 KB

georgecollier · 2024-09-28T06:49:57.532Z

crathbun:

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.

You’re absolutely right. You will be one of many to have to do this over the coming weeks

system · 2024-12-06T11:47:37.049Z

This topic was automatically closed after 69 days. New replies are no longer allowed.