Purpose:This article explains the cause of the “Oops – Invalid Interval” error encountered on the Shift Management Page within the SupportLogic instance and provides guidance on how to identify and resolve the issue. |
Cause:
The error occurs due to invalid schedule configurations for engineers. These issues typically involve one of the following scenarios:
I. Shift Schedule Misconfiguration
This occurs when the end time of a shift is set earlier than its start time, particularly across two consecutive days.
Example Scenario
A shift is scheduled from 6:30 PM to 3:30 AM.
If should be split correctly as:
6:30 PM – 11:59 PM
12:00 AM – 3:30 AM
However, if the new shift is created 12:00 PM - 3:30 PM for the following day, it creates a time conflict. This can trigger the “Oops” error not only on the Shift Management Page but also on other pages within the SupportLogic platform.
II. Out of Office (OOO) Misconfiguration
This happens when the end date of an engineer’s OOO schedule is set before the start date.
Example Scenario
An engineer is scheduled to be OOO on 13th and 14th February 2025. The OOO should be configured as:
Start Date: 13/02/2025
End Date: 14/02/2025
If the dates are mistakenly set from 14/02/2025 to 13/02/2025, the system may throw an error across various pages.
Recommended Action
Review all recent shift schedules and OOO entries for the engineer(s) in question.
Ensure all shift end times follow start times, especially when scheduling overnight shifts.
Confirm that OOO end dates occur after start dates.
Correct any misconfigurations found.
Note: Typically, the system prevents invalid date and time configurations. However, in certain edge cases, these invalid entries may be saved, leading to the error.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article