Troubleshooting: Scheduling After Organization Changes

These are common issues that occur in Workday Scheduling when a team is restructured or an organization is reorganized.

Schedules disappear during reorganization.

When you begin a reorganization, the scheduling organization (SO) may transition to operate under a different high-level scheduling organization (HLSO). When the new HLSO has different configuration settings, schedules may disappear.

Access the

Edit Scheduling Settings

task. Ensure these 4 settings from the previous HLSO match the settings on the new HLSO:

Start day of week.

Location and time zone.

Labor demand period length

Subgroup organization (SGO) settings, including SGO usage, SGO list, and SGO time zone.

If you need to change these settings for the new HLSO, you can either:

Access the

Edit Scheduling Settings

task for the new HLSO and create a new snapshot effective dated after the last existing schedule. You can then update the settings on the snapshot.

Clear the schedules associated with the previous HLSO settings and recreate them using the new HLSO settings. This applies whether the scheduling organization becomes its own HLSO, a new HLSO is introduced between the old and current HLSO, or if the scheduling organization now reports to a new HLSO.

When enabling a new high-level scheduling organization at the existing scheduling organization level or above the scheduling organization, configuration options are locked on the Edit Scheduling Settings task.

Some HLSO configuration settings are crucial for Workday to generate and display schedules. Workday prevents you from editing these settings in order to maintain data integrity when there are existing schedules, shifts, or labor demand for the HLSO.

During the initial snapshot setup for new HLSOs, Workday temporarily unlocks these four configuration options. It is essential to ensure that these settings align with those used in previous schedules:

Start day of week.

Location and time zone.

Labor demand period length.

Subgroup organization (SGO) settings, including SGO usage, SGO list, and SGO time zone.

Following the initial snapshot, if you identify errors in your configuration, you can use the Settings
tab on the Cleanup Invalid Scheduling Data
task to update these settings.

Removing subgroup organizations or changing the Start Day of Week using this task could make schedules disappear due to the reasons we’ve listed in the first troubleshooting issue. Workday recommends exercising extra caution and double-checking your configuration when using this task.

The schedule won't load after inactivating an HLSO.

When turning off an HLSO, existing scheduling organizations will continue to traverse up the organization chain to find an enabled HLSO with valid configuration to use for rendering the schedule.

These four configurations must be the same as the configuration used when the schedule was created.

Start day of week.

Location and time zone.

Labor demand period length.

Subgroup organization (SGO) settings, including SGO usage, SGO list, and SGO time zone.

Re-enable the HLSO, clear the schedule, then disable the HLSO and recreate the schedule under the new HLSO.

After a reorganization, Workday displays an error when you try to save new labor demand.

Schedule tags aren't being correctly inherited by the new scheduling organization.

Use the

Cleanup Invalid Scheduling Data

task to:

Clear all historical labor demand instances.

Clear tag sets for the current week.

Then, delete the corresponding labor demand and shifts.