Hey Keith, hope all is well with you in San Francisco!
It seems more elegant than using Bubble’s native
Schedule Workflow on a List because with List Popper, I can always save the not yet processed parts to the database with two upsides:
- Traceability: If the associated “processor” workflow fails for some reason, I can always restart it on the remaining list without having any confusion as to what was processed vs what wasn’t.
- Progress indication: This is basically also “traceability” but specifically that, because I have the known size of the unprocessed list stored somewhere, I can make UI feedback like:
As far as I know, this isn’t easily done with Bubble’s native
Schedule Workflow on a List, or am I wrong?
Anyhow, for all of these reasons, I want to stick with using List Popper for list iteration but I have one BIGish problem:
List Popper doesn’t seem to work on the
User data type
Basically, any “Popped” User items return nothing, zilch. Other datatypes with the exact same permissions and workflow do return expected data.
After fiddling for a while I finally just deleted all of my
User permissions (which is itself problematic) to make the
User type totally public. I thought, “That should make it work!” Alas, it didn’t. List Popper doesn’t seem to transmit
User data into any step of a workflow irrespective of permissions.
Have you been able to process a list of
Users using List Popper? Perhaps I’ve just made a simple mistake?