Schedule Optimization troubleshooting guide<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Introduction This knowledge base article offers an overview and serves as a high-level reference for understanding the Schedule Optimization log messages that occur during an optimization run. Overview After each optimization run, the corresponding logs can be found in the batch configuration record or the intraday job record that captures details such as the technicians considered, optimization horizon, tasks in scope, and applied constraints. Optimization logs show how each technician and task was handled. It also helps identify dropped technicians (those excluded due to invalid work schedules) and conflict tasks (tasks that could not be assigned due to scheduling conflicts). The log entries for an optimization run also contain debug-level messages that become visible when the Schedule Optimization property "Logging level" is configured to Debug. Categories The category identifies the specific stage within the optimization process at which the log message is generated. * Data Preparation * Job Scheduling * Events * Solution Processing * Task Assignment * Time Horizon Log levels * INFO — Indicates the current status of a process. No action is necessary. * WARN — Indicates that data issues were detected. The optimization run continues, but you should review the affected record and update the configuration as needed. * ERROR — Indicates an issue that affects the optimization run and may cause some qualifiers (assignment groups or territories) to be skipped. Follow the suggested resolution in the attached document to address the issue. * EXCEPTION — Indicates a critical failure that prevents the optimization run from proceeding. * DEBUG — Displays detailed information such as database queries, data dumps, and calculations related to the time horizon. Use this level when investigating further. For a complete list of log messages, including their category, importance, log level, and suggested resolution, see the attached document.