What about a separate database table (i.e. the main data object) for changes to the queue?
You can have separate actions for each (as you described), or you have one property (for example, โactionโ) in the object of the object with variables in the queue. Then you can either try it regularly, you can check the connection before trying to synchronize the changes, and, as you said, swipe through them and clear them of success.
source
share