Query running twice simultaniously mobile app

Hi! I'm experiencing a really weird issue with a mobile app. Since yesterday I've been having this extremely weird situation where a process in a retool mobile app is being executed twice almost at the same time (when it should've been just once).

The process is triggered after the confirmation window of a button, the query execution starts:

I later got a report that the outcome of the process was duplicated, while checking the audit logs I can see that all processes ran twice for some reason with a difference of milliseconds:

In short the process updates the balance sheet of a selected customer so it's quite sensitve. And in this case it duplicated the update which then required some manual adjustments and an audit on the complete workflow. There are over 1600+ successful runs on this process in production in the last couple of months and this issue just started happening yesterday.

I did many tests in staging and unfortunately I can't reproduce it. Today I'm seeing the same problem again with this process and additionally another process is showing the same behaviour, whatever query needs to run it runs twice with a millisecond difference.

Additional information:

Cloud Retool version 3.87.0
Issue has ocurred with multiple users and different devices, I believe only iOS

Is this a bug? Any tips or commendantions or any help is greatly appreciated?

1 Like

Experiencing the same issue. We have a mobile app with a bunch of forms that has been working just fine, until the recent 3.87.0 update which for some reason now duplicates the form submission. Instead of 1 form per submission, we get like 25!!! This isn't the first time happening where an update messes up something for an already working app. Very unreliable when can't get an immediate fix and have to wait couple of days for an answer!

Jesus, we had some financial loss due to this bug, too!

Procurement is being submitted twice every time a button is clicked.

1 Like

Same here. This just started for us.
Form submissions are running wild - hundreds of records being created sometimes, rather than just the one!

This is also happening for our tools and creating multiple bookings for a single transaction.

Same here. Every form submission that should result in one entry in the database, creates multiple entries instead. In my case, this results in 4 entries and sometimes even more. It is a critical bug and I hope retool staff is reading along since this is rendering my apps completely useless.

Hey folks, thanks for raising this. Is someone able to share an app export via DMs?

I wasn't able to repro on iOS/android with a form hooked up to retool DB. 1 insert -> 1 row


Due to the amount of folks reporting this, it sounds like a regression causing multiple triggers on the form submit button, but I'm hoping to reproduce to be able to file an incident. If anyone has any extra info like iOS version or resources being used that would be helpful too! Thanks in advance!

Update: We've reproduced and filed an incident for this.

Update 2: We're reverting the build and will be requesting an expedited review from Apple to get the iOS version reverted back asap. When the version is updated, you will be able to download the updated version from the iOS app store. Hard to give an ETA as this relies on them, but could be anywhere from (hopefully) a couple of hours -> up until tomorrow that they apply the build.

Update 3: The app has now been reverted and is available to download via the app store

2 Likes

Hi Isaac! Thanks for your input and we'll be looking forward for the revert of the app version, just to clarify my problem isn't with forms rather my button calls a sql query transaction instruction, however the behaviour is the same as the others reported. Hopefully the revert will help us out.

@Jose_Cifuentes @marc_denijs @jjsipin @hansontools @Roamify_App @Hussein_Ahmed Hey folks, the old build should now be available to download through the app store. Please let us know if you continue to see issues on the old version!

2 Likes

Hi @Isaac-H, on our end, the build seems to work again with our initial tests, and the SQL and API transactions now run as expected and not creating double or multiple bookings.

Thank you for your help!

3 Likes