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
"Sync Now" should synchronize "meta" database when pressed #7121
Comments
Ready for AT, PR #7122 , branch TestingThis is how I tested locally the changes:
|
Tested logging bugs don't sync with other docs but sync on Sync Now @mrsarm does this require a one day lag period for telemetry? Logged in as a new offline user. |
@newtewt yes because what are synchronized are the records from previous days (summarized in one record each day). Step 2 here suggests to change the clock time one day forward. Also not mention because it's unlikely: sentinel moves each XX time records from each user's meta DB to the |
Cool, just thought it to be odd that sync now still requires a daily cycle process to sync now. After adjusting my date the telemetry logged. I think this is working as expected and we can move on. |
Yes I myself got the same confusion testing the change 😄 |
What feature do you want to improve?
When users press "Sync Now" , only the device's main database is synchronized (the database with the reports, tasks, messages..). The "meta" database that contains feedback and telemetry documents is only synchronized by a cron job each 30 min, and if there is no connection by the time, another 30 min of waiting are needed to successfully synchronize.
Describe the improvement you'd like
When user clicks "Sync Now", the meta DB should also be synchronized. One synchronization shouldn't affect the sync of the another.
Describe alternatives you've considered
This was not requested by any particular partner or user, but would be a nice to have now that we are increasing the quality and sync frequency of "meta" data. Also is a one line patch, that going to attach to the issue.
Additional context
The size of the request needed to do the synchronization is still little data, it won't affect data caps if the data is synchronized with a mobile data plan instead of WiFi, because taking into account compression used by the devices and that only new data is syncronized, only a few kilobytes are consumed. Moreover, because we put the user in control of when to synchronize, we avoid waste of data spend by requests made automatically by the app because the user can choose to do the sync when is connected to a WiFi connection.
The text was updated successfully, but these errors were encountered: