Conditional logic broken? Duplicates are being allowed when they shouldn't be

Im sorry i continuing in this thread, but it is very interesting to understand how it works.

  1. Custom form had submitted by user.
  2. The data from custom form don’t emmideatly forced to Glide server, they will be synced only on next syncing cycle.
  3. Connection lost after custom form was send and stored to user device, but before local data have synced to server.
    Whats will be happened on connection restores? All local data will be purged and downloaded new one from server? Or unsynced part will be proceed to server first?
    Thanks Jeff for spending your time for discus!

Syncing should be almost instant. It’s not on a timed cycle. Usually within 1 to 3 seconds of clicking submit, a row is synced to the glide server and synced to all users devices.

As for a custom form that’s submitted…if the connection is lost immediately after the form is submitted and before it can sync to the glide server, I’m not sure how the app responds to that. I think we are talking about a one in a million shot if that happening since it’s probably a very small window for that to happen. I guess it’s something that could be tested with a computer that’s hardwired via an Ethernet cable. Press submit and pull the cable at the same time to see what happens.

In the same respect, if you used a third party service like Make to handle atomic operations, it may just fail if the call to Make can’t complete when the connection is lost.

The documentation isn’t clear if the Add Form and Add Row work the same when the connection is lost, so aim not sure about that. Add Row | Glide Docs

I’m not saying it’s all fool proof. Some things may slip by, but I think in real world cases, it’s rare.

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.