SYNCDATE DocsEvents 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.
Last updated
Open a sync and look at its issues list or its activity. When SYNCDATE can't apply a rule or leaves an event out, it says why in one line. This page is the list of those lines. For rules you wrote, the fix is nearly always in your Custom result or its conditions. See custom text and rules.
Could not be applied
An issue card is headed with the field name followed by "could not be applied", for example "Title could not be applied". The line under it says why.
The selected result has no title
"Add text or choose a title variable that has a value." Your Custom title came out empty for this event. Add fixed text, or pick a variable that always has a value.
The selected result is too long
The result is over the field's length limit shown in the message. That event isn't copied. Shorten the Custom result. See what SYNCDATE can't do.
The selected result needs an original value that is unavailable
The variable you used has nothing for this event, for example a field the provider doesn't supply. Use a different variable, or add a fixed fallback.
The destination cannot store the selected field value
The other calendar has no place to keep that value. You can't fix it with a rule. Choose a different field or accept that this value won't cross.
The destination rejected the selected value
"Check this field's Custom result." The other calendar refused what the rule produced. Simplify the result and save.
This Custom expression cannot be evaluated
"Review its conditions and result." A condition or result is incomplete or contradictory. Open the rule and fix it.
This event was not copied
"This event was not copied. Its time is not blocked by this copy." Or: "The existing copy remains with previous settings. This change, including any new privacy choice, was not applied." The copy kept its old settings until the issue above is fixed.
More issues could not be loaded
"More issues could not be loaded. Try again." Reload the list.
Skipped lines in the activity list
Each line starts with "Skipped" or a short label. Most are normal.
| What you see | What it means | What to do |
|---|---|---|
| "Skipped by your sync filters." | An exclusion matched, such as All-day events, a title word, or Free or Busy events. | Change the filter if you want it copied. See filter settings. |
| "Skipped because it falls outside this sync's date range." (Outside sync window) | The event is outside how far ahead or back the sync looks. | See how far ahead sync goes. |
| "Not copied because the other calendar didn't keep this event." (Not kept by the other calendar) | The other calendar discarded it. | Nothing is broken. See Working with limits. |
| "The other calendar does not show this occurrence, so it was not copied." | A repeating event runs past what the other calendar shows. | Nothing to do. |
| "Skipped because SYNCDATE had never copied this source event." | A removal arrived for an event that never had a copy. | Nothing to do. |
| "Skipped because the source recurring series is no longer active." | The series ended or was removed at the source. | Nothing to do. |
| "Skipped because a later change to the whole repeating series replaced this change to one meeting." | A newer series-wide edit won. | Nothing to do. |
| "Skipped because SYNCDATE couldn't read this change from the source calendar." | The source didn't return the change. | Wait for the next run. If it repeats, contact support. |
| "Skipped because this repeating series is linked to a different copy than SYNCDATE expected." | The series copy doesn't match its record. | Contact support with the series title. |
| "Already in sync" and its variants | The other side already matches. | Nothing to do. |
| "Managed by another sync" | A different sync owns the copy of this event. | Nothing to do. |
| "Superseded by newer change" | A newer edit replaced this one. | Nothing to do. |
| "Filtered by RSVP status" | Your RSVP filter excluded it. | See filter settings. |
| "SYNCDATE skipped this event." | No further reason is recorded. | If it should have synced, contact support. |
Related
Custom text and rules: decide what each copy says
Write a copy's title, description or location yourself with pieces of the original dropped in, and use if-this-then-that rules for text, privacy and free or busy.
Filters: which events get copied
Which events enter a sync at all: the RSVP filter, working hours, Google's special event types and exclude rules — plus what tightening one deletes.
What SYNCDATE can't do
The limits no plan removes: syncs don't chain, special event types are Google-only, feeds are read-only, and colour is approximate between providers.
Why events further ahead aren't copied
Your sync window is 30 days, 1 year or unlimited depending on plan. Why a healthy sync can still look incomplete, and what repeating events do instead.
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.
Why 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.
Why 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.
Messages when saving a sync
What each message means when SYNCDATE won't save, start, resume or delete a sync, and what to do next.