Different users using the same database at the same time, data gets tangled

Hi all,

I have an app that is essentially a request form. It collects various types of data, then gives it back on the next page for verification (in a repeating group), and if verified by the user (no log in necessary or designed for anyone), it sends the data in a table form to my email address as a request and resets all the data-fields.

My problem is that if two (or more) users are trying to use the app at the same time, their request data gets “tangled”. If they fill out the form (at the same time), both of their data shows up at the verification step and ends up being sent.

Does anyone have an idea how this could be avoided? The purpose that the app is used for makes it really inconvenient for the users to have to sign in, also for me to handle that. Is there a way to make it so that only the current user’s inputs are handled in their own process?

Thank you very much in advance!

The action (button) they click to go to verification needs to trigger a workflow that creates a new request and populates it with the data they entered on screen. The new request will have verified = no, then when they verify it, it will change it to verified = yes and trigger the rest of your process/workflows.