Reference: Scheduling Optimization Engine Error Messages

Error Message	Potential Cause	Solution
IllegalStateException: SchedulingOrganization has not yet been loaded for null OR SchedulingOrgLite has not yet been loaded for null	The time zone that is used on the HLSO is no longer supported or may have been retired. The processing user doesn’t have any scheduling organizations that they’re secured to. There is no valid configuration for the active HLSO.	Replace the time zone ID on the HLSO with another instance of the same time zone. To check this, access the Location listed on the HLSO, and navigate to the Business Site tab. Edit the Location and under Time Zone confirm it still exists in the drop down. Check for enabled scheduling organizations (or the organization the manager manages). Ensure that the organization is enabled as a scheduling organization, and whether there are security issues. Access the View Scheduling Organization Settings report. View the settings for the active HLSO. Look for the Start Day of Week and/or Location to make sure they’re accurate. Ensure that there is at least 1 tag type and 1 tag value.
RuntimeException: failed to read json string. Cause: cannot construct instance of…	The Inherit checkbox on the HLSO may have been selected and then unselected.	Select the Inherit checkbox on the HLSO again.
IllegalStateException: Could not find Tag IDs for Tag Set ID	The Schedule Tag Value was enabled and then disabled, and the schedule tag value exists on the Labor Demand or on a schedule.	Enable the Schedule Tag Value , then clear any labor demand with this schedule tag value, or rescind any published schedules with this schedule tag value. If this is in Production, keep the Schedule Tag Value enabled.
Time…not within the week time range…	If a schedule was originally created using one time zone (Example: EST), then reorganized to a different time zone (Example: CST) the schedule will disappear as Workday will load using the new time zone and won’t load the original time zone. The time zone between the two must match. If a shift time is outside of the scheduling week (using the subgroup organization time zone), this error appears because Workday creates the schedule using the HLSO time zone. Example: The HLSO time zone is EST but the SGO time zone is Hawaii. There will be a small gap on the schedule where the shift is outside of the EST week start and week end.	Submit a Workday Support Case with your customer tenant screenshots.
RuntimeException: Unexpected schedule... in previous schedules...	You changed one of the settings on the HLSO Settings tab. Examples include: Start Day of the Week Time Zone Labor Demand Period Length	Revert the changes back to the original settings, and then change the effective date of the HLSO settings and apply your changes with that new effective date.
failed to deserialize into an instance of class SchedulingError[]	The initiating action on the Publish Schedule business process security policy with the (REST) suffix doesn't have initiator listed.	This business process security policy must have the correct security groups listed. It cannot be blank.
TimePeriod{start..., end...} culd not be mapped to a week in '[TimePeriod{start..., end...}]'	The week is a Daylight Savings week. The start day of the week is on Monday.	Submit a Workday Support Case with your customer tenant screenshots.
We’re getting multiple errors: cannot deserialize org config and circuit breaker.	The Scheduling: Budget and Sales Data domain security policy isn't enabled.	Enable the Scheduling: Budget and Sales Data domain security policy.
java.net.SocketTimeoutException: timeout	The tenant UI has timed out. A stale page has the connection severed for security purposes.	Refresh the page to initiate the action again.