I’ve got my workflows set up that when a user clicks on a button on Page 1, it sends the data to Page 2 as a URL. My workflow on Page 1 creates a thing using backend workflows.
On Page 2 i’ve got a page load that when completed, sets the name of the first item in the database with added constraints by Created date. (I want to target the thing we just created on Page 1).
This works but sporadically, sometimes it works and sometimes it changes the 2nd thing in the DB instead of what we just created. I can only assume that there’s some timing issue like the content not being created in time so it targets the 1st item on the DB at the time?
Can anyone help/offer some thoughts to why this may be happening? Attached the constraints I have on Page Load.
On further inspection this seems to be a timing issue?
My backend API is taking longer than the next step in the same workflow that wants to make changes to the first item (therefore changes the 2nd item in the database as it’s still 1st if that makes sense).
I’ve tried to move the next step in the workflow to a new page and also gave it a pause interval but still works very sporadically. Any help would be appreciated.
Maybe you could try adding some on-page actions? IIRC, we can’t delay processes. By having things happening on screen (coupled with add a pause) - it should give you some delay for the search to take place.
Your search is straightforward. It shouldn’t take long, unless there are numerous entries. You could also try inheriting “Things to change” via “Result of step…” (although this one needs an extra step prior to your “Make a change”) or parent group.
Thanks for your help guys, your comments unlocked some new thinking for me. (I’m new to Bubble IO)
Not really a solve if you need to have a backend and frontend workflow run together but I managed to revise my architecture to put all my steps in the front end workflow and now it works perfectly.
