Forum Documentation Showcase Pricing Learn more

Why does scheduling an API workflow on a list take so long?

I have an API workflow set up to create new things connected to a project object. There are roughly 50-60 projects in the list. When I schedule an API workflow to run on this list of projects to create a new thing for each project, the blue loading bar at the top of the page appears and takes 30-60 seconds to finish. It seems as if this loading bar is shown as the API workflow is running, and if I look at the database they are all created by the time the blue loading bar has finished. My understanding was that the API workflows should run server side so the user is not waiting on the workflow to finish and slow down the UI. Am I missing something?

Something is not correct (you must have something running client side) scheduled API workflow is not client side so in effect you should not be seeing the blue progress bar. Sorry for the obvious question… What is the debugger saying

Alternatively screenshot of your workflow?

Here are some screenshots of the workflows.

If I do step by step in the debugger, it hangs on the “Schedule an API Workflow on a list” step until the API workflow has finished. I then get a message saying "Your application could have been 141 seconds faster since page load with more capacity. " I’m on a personal plan right now, but I tried boost and it didn’t make much difference.

Thats interesting thanks for the reveal…has this just started happening or is this net new?

The reason i mention it is that up until a few days ago, my schduled API workflows without issue. but over the last week… they hang (in the debugger like yours) until the whol;e API workflow in the backend has run.

I’ve tested sperate senarios to try and replicate…with much success. I think its worth submitting a bug report.

Also i noticed other threads on deleting things taking ages… maybe Bubble is changing stuff and this is the outcome

I haven’t noticed it on other API workflows, but I need to check the others to see if it does the same thing.

I have submitted a bug report and will update the thread with what I find out.

2 Likes

Having the same issue. My app has been slow for a while and I have just isolated this as the issue, app runs fast without a particular api running.

You might try having a “middle-man” endpoint to see if you achieve better results.

Create an endpoint which has the sole task of receiving a list and the let IT be the workflow that schedules the individual add_checklist_item calls. From the client side workflow, schedule an api (not schedule on a list) and pass the list as a single parameter to your middle man.

2 Likes

I’m confused. Are you saying that when running an api workflow on a list it should be fast enough that no blue bar would appear?

Yes, have had the same issue. ^^^^ is the answer.

1 Like

Would you mind providing a screenshot of how you pass the list as a single parameter to the middleman?

1 Like

+1 on API workflows on a list having become incredibly slow. I’m not sure if it finished the complete task though (at least in my case). I’m watching the result on a repeating group, and the blue bar disapperas before the results turn up (which could be delay in the list of course).

Building a middle-man workflow now, but did anyone notify Bubble about this?

Edit: @blake1 just noticed you did file a report. Did you get any new info on this?

@blake1 and others on this thread:
Any feedback from Bubble on this issue? I want to avoid having to go through the middleman solution if it all possible.

I was just about to create a new thread on this actually. Everything that involves lists seems to have slowed down considerably. Just adding or removing an item from a list takes around 25 seconds, and sending a list to an API workflow (not running the workflow on a list, but just sending a list as a parameter) can take up to a minute.

I’ll file a bug report if it persists, would be great to know if it’s just me or everyone.

1 Like

I am in early development so I have just a few test records that I’m working with. And my lists take 11s. Would grind the app to a halt when I get to prod.

Schedule up to 5 recurring event per thing

This is new for me. It mean for personal plan is 1 recurring event per thing.


What exactly does that sentence entail? That scheduling on a list on a Professional plan can apply to a maximum list count of 5?

As far as I know, this only gives the number of “Recurrning Events” that can be created. I did not see a restriction for “Schedule API Workflow on a list”. I have fourteen in my app with a “Professional Legacy” plan.

Yeah, I’ve been scheduling a shitload of lists over the last year, never noticing that :slight_smile:

But I’m still not 100% clear on this. Recurring event, I take it, are API workflows that have a repeated schedule, such as monthly or daily. It’s the per Thing that makes this confusing. I can schedule a limited amount of recurring Events per Thing?

How is that calculated? A repeated workflow can affect one, or hundreds, of Things?

Also, their pricing list says that Professional supports Daily schedules, but this list says weekly. Was this increased after the price changes? So legacy only as weekly?

I’m not sure, let me tell you, let’s hope someone corrects it if there’s a mistake.

You can create countless “Recurring Events” on the API workflow page, and only one data type is defined for each, and you can use up to 5 “Recurring Events” for each data type.

As with the New API Endpoint, you don’t have a chance to add many parameters. Just a “thing.” For example, User. And 5 repetitive events related to this thing.

Yes, unfortunately. The old plan was weekly, the new plan offers it daily.

1 Like