Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(autogpt_builder): Ensure we have insight into flow sync conflicts (client <-> server) #7308

Open
1 task
Pwuts opened this issue Jul 3, 2024 — with Linear · 0 comments
Open
1 task

Comments

Copy link
Member

Pwuts commented Jul 3, 2024

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:

  1. Save: send serialized flow to server
  2. Retrieve stored flow from server
  3. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant