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

Update Google event failed to save. Continue with synchronization? #2023

Open
ksuuk opened this issue Dec 10, 2024 · 7 comments
Open

Update Google event failed to save. Continue with synchronization? #2023

ksuuk opened this issue Dec 10, 2024 · 7 comments
Labels

Comments

@ksuuk
Copy link

ksuuk commented Dec 10, 2024

Are you already using OGCS?
Yes, 2.10.0.0

Describe the question you have
I have a laptop Mac and a separate VMware Guest Windows where OGCS 2.10.0.0 runs, now when I drive between home <> office etc, then laptop looses network connections and OGCS will no longer sync, giving popup - “Updated Google event failed to save. Continue with synchronization?” what stays forever despite the restored network connection.

Screenshot 2024-12-10 at 10 32 53

How to configure that OGCS always tries sync without asking for permission?

@ksuuk ksuuk added the question label Dec 10, 2024
@phw198
Copy link
Owner

phw198 commented Dec 15, 2024

As you've described, the issue is OGCS cannot sync when it loses network connection - so if you know that is going to happen, best to stop OGCS syncing beforehand.

There are other tickets with feature requests on specific sync times, automatic closure of popups etc, but I don't have an ETA on those features.

Meanwhile, you could reduce the frequency of syncs so it's less likely to be syncing when it loses network connectivity.

@phw198
Copy link
Owner

phw198 commented Dec 15, 2024

BTW, I would recommend you update to the latest beta release, v2.11.0.

@ksuuk
Copy link
Author

ksuuk commented Dec 15, 2024

BTW, I would recommend you update to the latest beta release, v2.11.0.

@phw198 I tried v2.11.0, but it didn't work at all, the application is running in the background (according to the task manager), but there is no GUI.

@phw198
Copy link
Owner

phw198 commented Dec 15, 2024

Did you upgrade or download and run the install executable for v2.11.0? If the latter, would be helpful to see the logfile when the application doesn't display.

@ksuuk
Copy link
Author

ksuuk commented Dec 15, 2024

As you've described, the issue is OGCS cannot sync when it loses network connection - so if you know that is going to happen, best to stop OGCS syncing beforehand.

There are other tickets with feature requests on specific sync times, automatic closure of popups etc, but I don't have an ETA on those features.

Meanwhile, you could reduce the frequency of syncs so it's less likely to be syncing when it loses network connectivity.

@phw198 Stopping OGCS every time I close the laptop lid and starting OGCS every time I open the laptop lid is annoying. :)

And the frequency is set to 2 hours, but the logic says that if OGCS cannot synchronize due to a connection loss, then the next time (after 2 hours) when the network connection is restored, OGCS should synchronize again, but this never happens because the application is waiting for user intervention.

@ksuuk
Copy link
Author

ksuuk commented Dec 15, 2024

Did you upgrade or download and run the install executable for v2.11.0? If the latter, would be helpful to see the logfile when the application doesn't display.

@phw198 I stopped v2.10.0.0, downloaded and installed v2.11.0. I tried several times, with the same result.

@phw198
Copy link
Owner

phw198 commented Dec 15, 2024

And the frequency is set to 2 hours, but the logic says that if OGCS cannot synchronize due to a connection loss, then the next time (after 2 hours) when the network connection is restored, OGCS should synchronize again, but this never happens because the application is waiting for user intervention.

With the evidence available (a screenshot), that's because it's actually in the middle of synchronising - ie you shut down right when it's actively syncing in the 2-hourly run.

Of course it might not be - it might have hit a problem ages beforehand with that error message and then you shutdown anyway and only notice the problem after you have resumed. I have no way of knowing without a log file, just going by what you said in the OP.

If there was a problem before you shutdown, then that root cause needs identifying...

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

No branches or pull requests

2 participants