Troubleshoot Shift Builder

You can create a Dataview that provides detailed information about issues that occur when the Shift Builder is run and schedule patterns are rolled out onto the schedule. You can use this information to troubleshoot and resolve any schedule building issues.

To create the Dataview and review errors:

Create an Employee Dataview. For more information, see Create a Dataview.
Define the set of columns using the following Employee Schedule Pattern-specific columns. For more information, see Select columns for the Dataview.
Note: These Dataview columns do not differentiate whether the processing type for the Employee Schedule Pattern is based on an individual Employee Pattern or Group Inheritance.
- Employee Pattern Name— Name of employee Schedule Pattern
- Employee Pattern Created By— User who creates the employee Schedule Pattern
- Rollout Start— Start date of pattern rollout period
- Rollout End— End date of pattern rollout period
- Rollout Failure Date(s)— Date(s) of the error-producing schedule item
- Rollout Failure Type— Type of failure
  - Functional Failure (for example, locked days)
  - System Failure
- Rollout Outcome— Completion state
  - Partial Success (Some schedule items rolled out but not all of them)
  - Failure (No schedule items rolled out)
- Rollout Failure Details— Error message returned from system
- Failure Report Anchor— In Assignment, select one of the following options. In addition, set Visible to No in the Column Properties.
  - Rollout Launch Date (Shift Builder Execution Date): Displays Shift Builder errors arising in the period generated by the Shift Builder on the rollout launch date, within the loaded Dataview period. If a rollout launch is not within the loaded Dataview period, the Dataview does not capture any errors.
    Example:
    - The rollout launch dates are July 1, July 8, and July 15, 2024.
    - Suppose the loaded Dataview period is set to July 6 to July 13. Since the loaded Dataview period is set to those two dates, any errors that are incurred from the Shift Builder execution (rollout launch) on July 8 will be captured.
    - Suppose the July 8 rollout produced Period 2. All the errors that are contained within that Shift Builder execution will be captured; in this case, the error that occurs on July 3, 2025.
  - Rollout Failure Date(s): Dataview identifies Shift Builder errors that occur within the loaded Dataview period.
    This option is recommended for managers to understand immediate issues.
    Example:
    - The rollout launch dates are July 1, July 8, and July 15, 2024.
    - Suppose the loaded Dataview period is set to August 10 to August 15. Since the loaded Dataview period is set to those two dates, and there is an error on August 13, the Dataview will capture that error.
  - Rollout Period(s): Dataview pulls in errors in the loaded Dataview period, as well as all other errors that occurred in the rollout event (includes all errors in schedule rollout periods that overlap with the loaded Dataview period).
    This option is recommended for managers who may want to see what other errors may have happened from the Shift Builder event when they know an error occurred on a particular day.
    
    Example:
    - The rollout launch dates are July 1, July 8, and July 15, 2024.
    - Suppose the loaded Dataview period is set to September 8 to September 15. While it appears that there are no errors during that period, the loaded Dataview period overlaps with Period 1. Therefore, all errors that occur from the period start date to the period end date are captured. In this case, Error 1 that occurs on August 13 and Error 2 that occurs on November 12.
In Dataviews and Reports > Dataview Library, select the Dataview and specify the desired date range. All Shift Builder errors are displayed, including but not limited to the following:
- Rollout before signed off date is not allowed
- Rollout before employee hired date is not allowed
- Rollout on inactive employee is not allowed
- Rollout on employee with terminated employee status is not allowed
- Rollout on locked days is not allowed
- The primary org job is expired
- Scheduled PCE exists on date of rollout
- Accrual balance overdrawn