We have an issue on avoiding duplication of records due to same Update transaction getting triggered.
When a transmit is triggered calling a transaction with Update step but wifi is not available, the transaction is getting queued on the client. When the user hits transmit again, a new instance of the same transaction is triggered causing a duplication of records sent to the backend. The number of duplicates depends on how many time the transmit was triggered before a successful transmit happens. There are no errors in the client or in the backend, but only the wifi connection prevents the successful transmit of the transaction.
We tried to use "Merge transaction" but it does not work for same Edit transactions.
How do we prevent or overwrite the transaction in the queue with the same key?