You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The commit seems to hang indefinitely if the client is offline, and it looks like this is intended behavior. After connection is restored, the commit is executed. How is this useful? It can freeze the entire app! I want to understand the use case for this. That doesn't happen with a Transaction for example, where if the client goes offline an error is raised and you can handle it.
If an error happens when trying to commit, is the batch discarded, or can I attempt to commit again the same batch? I couldn't forcibly make the batch fail, so I couldn't test this.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Thank you for your time.
Beta Was this translation helpful? Give feedback.
All reactions