So my understanding of @keith’s message is neither solution should work reliably… yours or mine.
And unlike what is suggested in the message, on my instance the iteration NEVER completes and fully updates the database.
I can wait forever and nothing happens on a list of 4 items. Keith’s “Iteration complete” action fires off after 2 iterations, one with a pause.
So that is curious in and of itself.
Keith can of course correct me but it seems as if you’re getting lucky at this point and your solution will likely break pretty quickly for Bubble being silly type reasons as it has in mine.
Reading through the bajillions of replies I think I caught Keith mentioning something about using List Shifter to create a list of Things and then saving the list to a list in the parent Thing.
In my example, have a field called “list of exercises” and then replace that list after a save button is fired.
Then the list should appear on the page in the order saved.
Considering this is a demo app and the list will only have a few items…
… I am less concerned about what I understand (probably wrongly) to be the security and data weight reasons why this is not the best idea.
Am I completely out to lunch?
@rico.trevisan when rereading your original message I think there is a misunderstanding with what is happening on my side.
I don’t think there is a queue backlog as it never “looks ok on the front end”.
The iteration works and the backend is updated fine for two items only. The “iteration complete” event is thrown then with Debug Buddy suggesting to me that the whole operation has stopped, and backed up by the fact nothing happens after.
Did I understand what you were saying incorrectly?