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

Fix: Sync Feature #431

Closed
mit-27 opened this issue May 17, 2024 · 1 comment · Fixed by #467
Closed

Fix: Sync Feature #431

mit-27 opened this issue May 17, 2024 · 1 comment · Fixed by #467
Labels

Comments

@mit-27
Copy link
Contributor

mit-27 commented May 17, 2024

Issues

  1. Unified GET APIs will not return data until the initial sync is complete. Once the sync is finished, data will be available in the database for Unified GET APIs.
  2. Unified objects are associated with each other. Currently, synchronization for all unified objects occurs in parallel, which assigns null values to the foreign attributes of these unified objects.

Possible Solutions

  1. Once the connection is created, the initial sync should trigger which stores the data from the third-party provider to DB. After that, the periodic sync can happen according to the user's settings.
  2. Maintain the sync order for unified objects based on their associations. For instance, the ticket object depends on the collection object, so in this case, we need to sync the collection object first, followed by the ticket object.
@mit-27 mit-27 added the backend label May 17, 2024
@mit-27
Copy link
Contributor Author

mit-27 commented May 28, 2024

Hello @naelob , I am working on this issue.

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

Successfully merging a pull request may close this issue.

1 participant