Riva Data Sync Error: [ErrorOccurrenceCrossingBoundary] Modified Occurrence Is Crossing or Overlapping Adjacent Occurrence

Rawan Maarouf
Rawan Maarouf
  • Updated

Issue

You may see one of the following errors in your Riva Cloud or Riva On-Premise synchronization logs:

WARN  Service response error: [ErrorOccurrenceCrossingBoundary] Modified occurrence is crossing or overlapping adjacent occurrence.

ERROR Unable to update appointment with occurrence crossing boundary error, due to missing preupdateStartDate

[Appointment] Error - Error occurred updating item: Modified occurrence is crossing or overlapping adjacent occurrence.
Modified occurrence (StartTime: 6/2/2019 7:00:00 PM, EndTime: 6/4/2019 12:00:00 AM) 
is crossing or overlapping an adjacent occurrence 
(StartTime: 6/2/2019 12:00:00 AM, EndTime: 6/3/2019 12:00:00 AM).

Cause

This error occurs when a recurring appointment in a series has been moved or edited so that it crosses into the time range of a neighbouring occurrence in the same series.

Each occurrence in a recurring series is separated by a strict time boundary (“wall”). 

If one occurrence is dragged, edited, or rescheduled in Outlook so that it overlaps or extends past the start or end time of an adjacent occurrence, the synchronization fails.

This behaviour mirrors Outlook’s own handling of recurring appointments - Outlook itself will prevent users from moving a recurring occurrence across another one in the series.

Example

Original schedule:

  • Occurrence 1: June 14, 2012 – 4:30 PM to 5:30 PM

  • Occurrence 2: June 28, 2012 – 4:30 PM to 5:30 PM

After edit:
Occurrence 1 is rescheduled to start June 28, 2012, at 4:30 PM, overlapping Occurrence 2.

Riva detects that the edited appointment now crosses into the next occurrence’s start time, and the sync fails with the ErrorOccurrenceCrossingBoundary message.

Resolution

To resolve this error:

  1. Open the recurring series in Outlook or your CRM.

  2. Identify and correct the overlapping occurrences.

    • Either move one of the occurrences so they no longer overlap, or

    • Delete (cancel) one of the conflicting appointments.

  3. Allow Riva to perform the next synchronization cycle - the error should no longer appear.

Additional Notes

  • This issue is not caused by Riva itself; it reflects a constraint within Exchange/Outlook calendar logic.

  • If you repeatedly encounter this error, verify that the recurrence pattern is consistent and that no custom or manual edits have shifted occurrences into overlapping ranges.

AppliesTo

  • Riva Cloud
  • Riva On-Premise