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

Aha, guess I haven’t been studying these closely enough. I’ve always tried to avoid using them, as they’ve felt limited. Guess this confirms that :stuck_out_tongue:

Anyway, thanks for the info!

Sorry for hijacking the thread @blake1 lists are still slow indeed for me.

Sorry to revive a thread a year old, but I am also having this same issue and have not quite been able how to figure out the “Middle Man” solution above.

Basically I am pulling a list of restaurants from Yelp’s API. I can get 50 at a time, but pulling each and entering them all into my database takes pretty long.

How exactly do I use this middle man concept with my original endpoint?

I never got an answer from Bubble on this, and I’m still seeing the same behavior. Anyone else?

I often struggled with scheduling workflows on list. Even with small lists. I ended up sharpening my skills with recursive workflows.

2 ideas:

  1. Could you try deleting the interval? It should show a red box around it, but it will still run.
  2. This one is a bit random. Duplicate that workflow, deactivate the original, and run the new workflow. I’ve once had a weird issue where this “turning it off and on again” technique made the weirdness go away. :person_shrugging: