Field Service Management Tasks Excluded from Schedule Optimization Due to schedule_next_day FilterIssue Work order tasks returned to the Pending Dispatch state are not being picked up again by Schedule Optimization and remain unassigned. Symptoms Work order tasks are removed from the schedule and moved to Pending Dispatch. Tasks remain unscheduled after returning to Pending Dispatch. Schedule Optimization does not reassign the affected tasks. The behavior may occur when tasks are removed from the schedule by system scheduling activities or when technician availability changes. Facts Multiple Schedule Optimization batches include a task filter that requires schedule_next_day to be false. The affected tasks had schedule_next_day set to true. Tasks with schedule_next_day set to true were excluded from the majority of optimization batches. The FSM 24 Hour Daily batch includes tasks where schedule_next_day is true. When processed by that batch, affected tasks could still be returned as infeasible and remain unassigned. Release Not release specific. Cause The optimization batch filters excluded affected tasks because schedule_next_day was set to true while the batch criteria required schedule_next_day to be false. As a result, the tasks were not submitted for optimization by most optimization batches. Resolution Review the optimization batch configuration and task filter criteria associated with Schedule Optimization. Verify whether schedule_next_day is preventing affected tasks from being included in optimization batches. Tasks that are not selected by optimization batches will remain in Pending Dispatch and will not be considered for scheduling until they meet the applicable batch filter criteria.