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
It is undesirable but possible that the server — due to differences in logic or syncing issues — has a different version of a flow than the client. To circumvent this, we currently have the following workflow for saving/syncing a flow:
Save: send serialized flow to server
Retrieve stored flow from server
Replace local version of flow with retrieved version from server
In addition to this:
we should be logging events where the server-side version (retrieved at step 3) differs from the version submitted at step 1.
This is essential for catching and patching data integrity issues.
We could log events like this to Sentry.
The text was updated successfully, but these errors were encountered:
It is undesirable but possible that the server — due to differences in logic or syncing issues — has a different version of a flow than the client. To circumvent this, we currently have the following workflow for saving/syncing a flow:
In addition to this:
This is essential for catching and patching data integrity issues.
We could log events like this to Sentry.
The text was updated successfully, but these errors were encountered: