-
Notifications
You must be signed in to change notification settings - Fork 654
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
Suggestion: Send an email to user when sync has reached max_retries #3501
Comments
Like it Forcing the sync manually gets the sync table back, right? |
If you force it, it gets synced if the datasource is still ok. But: A doubt I have is that the retries are not going back to 0 when you force one (I think), as far as i've seen by investigating the logs. (Check retried times with values 11 & 12, when maximum is 10 if i'm not wrong) |
oh, this could be what's causing our issues. If the retry count doesn't get A retry count of 10 can easily be met in a few months of syncing just due On Tue, May 5, 2015 at 1:52 PM, Carla notifications@github.com wrote:
David González |
I really don't know how it works really, it was just guessing after what I've read in the code, so we'd need an expert adding the details here :) Edit: It's reseted:
|
@saleiva I'm going to need the mail body for this :) |
Due @saleiva is on vacation @carlostallon @piensaenpixel please give some feedback here to close this :) |
Cool! I have two questions:
|
+1 the first point ok. The link goes here, http://docs.cartodb.com/cartodb-editor.html#error-codes-and-solutions |
Ok, thank you :))) |
@ethervoid this copy better, sorry The automatic synchronization of dataset “XXXX” has reached the maximum number of synchronization attempts—and is still failing to synch. If you'd like to continue trying, log in to your account and manually reactivate synching by clicking “Sync now.” |
@piensaenpixel what do you think? |
Feedback from @d4weed
When a sync table fails to be synced and it gets to "max retries", it's never synced again. We could warn the users through an email that this is happening so that they're aware that their data will be no longer updated.
cc @saleiva
The text was updated successfully, but these errors were encountered: