Hey everyone! Hoping the community can help me rule out a major issue I found. A bug got reported by a user on a live app I have that runs a workflow on a list.
The lists usually contain between 100 and 500 items.
The API changes about a data field on each item in the list. For example, let’s say the API runs on a list of Fruit in the user’s account.
It goes through each Fruit, and changes “is tropical fruit” from “no” to “yes” (yes/no data type).
After the user reported the bug, I looked into the DB, and found that about 30-40% of the items in the list were unchanged. Since the rest worked perfectly, it doesn’t seem like it’s a bug, it’s like the API just didn’t affect certain items.
I didn’t think a few hundred items was long, but after reading this (Schedule API workflow on a list - does the list have a limit?), I wondered if that could be the issue and if “run workflow on list” is inconsistent.
This was another breakdown by a Bubble user, who essentially said workflows on lists are more unreliable (but faster), while recursive workflows work 100% of the time (but are slower). Incomplete Schedule Workflow on a List
Also read that @romanmg recommended someone do a recursive workflow to fix this problem.
I’m willing to upgrade to a higher paid plan (I’m on personal legacy right now) but before I do that, I wanted to see if you all think it’s a core issue with the API workflow on list. If I need to switch to recursive workflows, I’ll take the time to do that.
Thanks in advance!