Hello fellow bubblers!
Has anyone of you experienced a limitation on scheduled events before? I’m scheduling backend workflows on lists, some at the same time when importing a data object. However, what I notice is that often when the list has 69 items, it only schedules 54 or 32. It just stops…
I’ve tried adding an interval and postponing certain flows but it keeps happening. No conditionals, just lists and workflows running at the same time.
Yes, I have had this problem before when adding items to a list in a database entry. So what I did was spread out the additions to the list by, for example, 1 second and it seems to work. In my instance, users upload a list using a CSV so I included a second column just called “row” and have the values count up sequentially (1,2,3,4, and so on) and then schedule the API with current date/time+seconds:the rows value.
Yes, this is a common thing involving lists and the back end workflows. A few solutions I have found are the following.
Can you share your settings? Are you calling an API in your workflow? (Not on the schedule on a list itself). Are you on the new schedule on a list version?
Interesting approach, do you then trigger these workflows when a row is imported or new data is added? Problem is that sometimes I have a list of 160 and then it would take so many seconds to complete
@dbom009 thanks, especially the second option I’ve haven’t tried. I will give it a go to see if that does the trick
@Jici Yes I’m scheduling on a list and calling the API workflow from a backend workflow. Here’s an example setting
I said to share what you have inside your workflow. What I believe is that you are calling a third party API and may reach the API call limits.
