Troubleshooting shift generation

This chapter provides troubleshooting guidelines for the Shift Generation feature in Advanced Forecasting.

This table shows the common issues that may occur in Advanced Forecasting, along with recommended resolutions for each:


Issue	Details and resolution
Shifts not generated	Verify that workload requirements are defined for the selected team and date range. Ensure employees are assigned to the team when the unassigned option is not used. Confirm that the user has the necessary security permissions to perform the task.
Job Scheduler task fails	Verify that the Solution Time Out value is sufficient. Increase it to 420 seconds if required. Confirm that task parameters are correctly configured, including Team and Minimum Day Offset. Review system logs for specific error messages related to the task execution. Ensure that the Auto-Assignment Scheduler task is running continuously.
Incorrect number of shifts generated	Review workload requirements against existing unassigned shifts. Verify the Create Unassigned Shifts Only setting and the associated gap-filling logic. Confirm that the Minimum Transition Length and Maximum Transitions parameters are configured correctly. Ensure the appropriate Staffing Requirement Generation Option is selected.
Unable to access Workload page	Confirm that the user has the required security permissions to access workload data. Verify that the feature is enabled in the WFM instance.
Workload not displaying after selection in the Forecast	Verify that forecast data is generated for the selected team and date range. Confirm that a valid Staffing Requirement Template (SRT) exists for the team. Ensure that the selected date range contains workload data. Refresh the page, then reselect the team and date range.
Unable to create or modify the workload	Ensure that a valid SRT is selected before creating workload. Verify that the user has modification permissions for workload data. If editing workload in a forecast, confirm that the forecast is generated before creating the workload.
Duplicate Driver error on ADD Operation	When a duplicate driver error occurs during an ADD operation, the system displays the message: `A record could not be added because it already exists in the system as defined by uniqueness rules.` To resolve this error, ensure the combination of the driver name and team name is unique in the system. Check the existing drivers for the specified team before adding a new one, and if you intend to modify an existing driver, use the UPDATE operation instead of ADD.
Unable to update or delete the Driver	If this error message is displayed: `A record could not be updated or deleted because forecasts in the system depend on it.` Then, delete all forecasts generated for this driver before attempting an UPDATE or DELETE. If this error message is displayed: `A record could not be updated or deleted because staffing requirements in the system depend on it.` Then remove the links between staffing requirements and the forecast driver before performing an UPDATE or DELETE. Note: UPDATE and DELETE operations are still allowed even if a data source is tied to the driver.