SYNCDATE DocsWhy is my sync on hold
The headlines a sync shows when part of its work is on hold, such as Restore calendar access or A change couldn't be confirmed, and what to do for each.
Last updated
"Sync on hold" means SYNCDATE chose not to change something, because it wasn't sure. A hold is different from a pause: the sync keeps running and the rest of your events keep syncing. The headline under the status tells you what is held. Find it below. If you see "Paused" instead, go to why my sync is paused.
Where the cure is waiting, the page says so. Where only support can help, it says what to send: the name of the sync and the address you sign in with, to support@syncdate.app.
Some changes are taking longer than usual
SYNCDATE is trying again automatically. You don't need to do anything. If the headline is still there after several runs, contact support.
Restore calendar access
SYNCDATE can't access one of this sync's calendars, so copies may be out of date. Review that calendar's permissions and reconnect the affected account.
You may also see this headline on a first copy that can't finish because access to a calendar was denied. Review that calendar's permissions or ask its owner to restore access. If that doesn't help, contact support.
See account and connection messages.
One or more events can't be updated yet
SYNCDATE can't confirm which event this is on your calendar, so it hasn't changed the copy. Everything else keeps syncing. Nothing to do. If it stays for a long time, contact support with the sync's name.
A change couldn't be confirmed
SYNCDATE made the change but can't see it clearly on the other side. Everything else keeps syncing. Check the event on the other calendar. If it is wrong there, contact support.
An event was left untouched
SYNCDATE couldn't tell whether the event was copied from another calendar, so it left it alone to avoid duplicates or deletions. Nothing is lost. If you expected this event to sync, contact support with its title. See also what SYNCDATE decides on its own.
A repeating event can't be checked
SYNCDATE can't verify one of your repeating events right now, so it hasn't changed its copies. Everything else keeps syncing. If it stays, contact support with the event's title.
Working with limits
Some events couldn't be saved in the other calendar because it doesn't keep them. Everything else is syncing normally. The same words appear as a status; see Working with limits.
A calendar setting needs checking
SYNCDATE couldn't confirm that a settings change reached the other calendar. You can't clear this yourself. Contact support and say which setting you changed.
Applying your settings change
SYNCDATE is applying your latest settings to your existing events. This can take a while on large calendars, and it needs nothing from you. If SYNCDATE makes no progress for an hour, the status returns to "Sync on hold".
First copy: the four headlines
These appear only on a new sync that hasn't finished its first copy.
Reconnect your calendar account
SYNCDATE can't finish the first copy because the account sign-in stopped working. Reconnect the account to continue.
Source calendar unavailable
SYNCDATE can't finish the first copy because the source is unavailable or can't be read. Check the source calendar, or contact support.
Calendar access needs review
SYNCDATE can't finish the first copy and can't yet tell whether the account sign-in or a calendar permission caused it. Contact support.
First copy needs attention
SYNCDATE has made no progress on the first copy for over a day. Contact support so it can be checked safely.
Sync on hold, with no other headline
SYNCDATE is holding the sync but doesn't know the reason well enough to name it. Wait for the next run. If it stays, contact support.
In the activity list
Each run in your activity list carries a result word.
| What you see | What it means |
|---|---|
| "Done" | The run finished. |
| "In progress" | More work is queued and continues automatically. |
| "On hold" | Some changes were held. See the headlines above. |
| "On hold — no changes made yet" | The run held everything and wrote nothing yet. |
| "Unconfirmed" or "Couldn't confirm this run finished" | SYNCDATE can't prove the run completed. It checks again on later runs. |
| "Issue" or "Something went wrong — no changes were made" | The run ended with an error. Nothing was changed. |
| "A sync run didn't finish — we retry automatically" | It happened on our side. There is nothing for you to fix. |
| "SYNCDATE couldn't process this event. Try syncing again; if it keeps failing, contact support." | One event failed. Try the sync again, and contact support if it keeps failing. |
Related
What each sync status means
Every status a sync can show on your dashboard, from Up to date to Sync problem, what it means and what to do about it.
Why is my sync paused
Every Paused label a sync can show, what caused it, whether you can resume it yourself and when to contact support.
Account and connection messages
What each account status, calendar access label and connection error means when you connect Google, Microsoft, iCal or CalDAV, and how to fix it.
Sync is active but events are not showing
What to check when a sync looks healthy but an event has no copy: direction, filters, how far ahead, then one Re-sync.
What SYNCDATE decides on its own
The moments the product acts without asking: two calendars changing one event, an account that stops letting us in, a downgrade that removes copies, and a calendar that isn't yours to write to.
Why is my sync paused
Every Paused label a sync can show, what caused it, whether you can resume it yourself and when to contact support.
Events that were not copied
What the issue cards and skip lines in a sync's activity mean when an event was not copied or a rule couldn't be applied, and how to fix each.