Schedule Optimization properties
You can set parameters that control how optimization runs.
Field Service Schedule Optimization properties
Schedule Optimization general properties
|
Property |
Description |
|---|---|
|
Exit buffer time |
Amount of time (in minutes) to add between the end of a task and the travel start of the next. An example of a valid time value is 10.- Type: Integer
|
|
Qualifier type for schedule optimization |
The qualifier type for schedule optimization determines the criteria used to optimize schedules. There are two qualifier types available: "Assignment group" and "Territory."When the Field Service Territory model is enabled, the qualifier type automatically switches to "Territory" and remains fixed. This means that when the Territory model is active, the optimization process focuses on territories instead of assignment groups. For more information, see Enable the Field Service territory model.
|
|
Number of seconds used for task scheduling resolution |
Specifies the acceptable interval for scheduling a task. For example, the value is set to 300 seconds. Schedule Optimization will schedule tasks and the associated travel time, such as task start, travel start, or estimated end, to the nearest 5-minute start or end time.
|
|
Maximum number of overlapping qualifiers in a qualifier set |
Numeric value set to determine the maximum number of overlapping qualifiers that can be applied to a single qualifier set.- Type: Integer
|
|
Logging level |
The logging level will determine the type of information displayed in the results of an optimization log entry, providing details about the Schedule optimization run. There are four options available: Error, Warning, Info, and Debug.- Type: Choice
|
|
Property |
Description |
|---|---|
|
Maximum number of location points allowed in a map vendor call |
Numeric value set to determine the maximum number of location points allowed in a map provider call. Beans.AI is the map provider that Schedule Optimization supports for travel time estimates. For more information, see Schedule Optimization travel estimate providers.
|
The following system properties are installed with Schedule Optimization.
|
Property |
Description |
|---|---|
|
sn_schedule_optim.so_max_batch_duration |
Maximum duration between start and end time on a batch run, in hours.- Type: Non-zero integer (in hours)
|
|
sn_schedule_optim.so_min_batch_duration |
Minimum duration between start and end time on a batch run, in hours.- Type: Non-zero integer (in hours)
|
|
sn_schedule_optim.consider_overlapping_territories_for_scheduling |
Controls whether overlapping territories are considered when scheduling tasks during optimization.- Type: True/False
|
|
sn_schedule_optim.max_priority_events |
Maximum number of prioritized event types that can be configured to trigger optimization.- Type: Non-zero integer
Note: The 'maint' role is required to edit this property. This role is exclusive to internal users. Contact support to make changes. |
|
sn_schedule_optim.intraday_assignment_horizon_offset |
Specifies the time offset (in minutes) added to the current time when calculating the window start for tasks that have no defined window start.- Type: Non-zero integer
|
|
sn_schedule_optim.intraday_max_retry_count |
Specifies how many times the solution processor retries submitting an intraday optimization job.- Type: Integer
|
|
sn_schedule_optim.intraday_minimum_frequency |
Defines how frequently intraday optimization runs.- Type: Non-zero integer
|
|
sn_schedule_optim.intraday_policy |
Specifies the default policy for intraday optimization. This can be overridden at the group level.- Type: String
|
|
sn_schedule_optim.intraday_qualifier_type |
Specifies whether intraday optimization runs by assignment group or territory.- Type: Choice list
|
|
sn_schedule_optim.intraday_window |
Defines the default schedule that controls when intraday optimization can run.- Type: String
|
|
sn_schedule_optim.max_agent_count |
Limits the number of technicians considered during on‑demand and intraday optimization runs.- Type: Non-zero integer
|
|
sn_schedule_optim.max_task_count |
Limits the number of tasks considered during on‑demand and intraday optimization runs.- Type: Non-zero integer
|
|
sn_schedule_optim.processing_time_per_task |
Specifies the maximum processing time, in seconds, that the optimizer can use to compute a solution.- Type: Non-zero integer
|
|
sn_schedule_optim.run_summary_packet_size |
Controls how many records are grouped when generating optimization run details.- Type: Non-zero integer
|
|
sn_schedule_optim.scheduled_state_count_of_task |
The number of work order tasks that can be in a scheduled state before being assigned to a technician.- Type: Non-zero integer
|
|
sn_schedule_optim.schedule_optimization_qualifier_type |
Specifies whether schedule optimization runs by assignment group or territory.- Type: String
|
|
sn_schedule_optim.schedule_state_type |
Determines how tasks are scheduled. The choices are duration or number of tasks.- Type: Choice list
|
|
sn_schedule_optim.scheduling_resolution_time |
The number of seconds Schedule Optimization uses to round task start times, travel times, and end times.For example, a value of 60 rounds all start times, travel times, and end times to the nearest minute. A value of 300 rounds them to the nearest 5 minutes.
|
|
sn_schedule_optim.logging.verbosity |
Sets the level of detail captured in Schedule Optimization logs for each run. The choices are info, debug, warn, and error.- Type: Choice list
Note: The 'maint' role is required to edit this property. This role is exclusive to internal users. Contact support to make changes. |
|
sn_schedule_optim.so_max_solution_threshold |
Maximum number of ML solutions that can run simultaneously. When workload distribution is enabled with multiple jobs or multiple optimization modes run concurrently, increase this value.- Type: Non-zero integer
Note: The 'maint' role is required to edit this property. This role is exclusive to internal users. Contact support to make changes. |
|
sn_schedule_optim.enable_qualifier_split |
Determines which optimization modes use split qualifiers to distribute workloads across parallel jobs. Choices:
Note: Split qualifiers work with batch, intraday, and prioritized optimization but not on-demand optimization.
|
|
sn_schedule_optim.qualifier_distribution_splits |
Number of splits to distribute qualifiers across parallel optimization jobs for each batch or intraday configuration. Higher split counts reduce processing time per job but require more ML capacity.If running multiple optimization modes simultaneously adjust
Note: The 'maint' role is required to edit this property. This role is exclusive to internal users. Contact support to make changes. |
|
sn_schedule_optim.maximum_matrix_size |
Determines the maximum number of locations that can be queried to a third‑party map provider when computing travel estimates.- Type: Integer
|
The following is the list of intraday prioritized event properties that are available with the Schedule Optimization[var.schedule-optimization] plugin. These properties configure prioritized event buffering, event thresholds, and limits on agents and tasks to optimize performance for time-sensitive scheduling changes. To access these properties, navigate to All > Schedule Optimization > Administration > Properties.
|
Property |
Description |
|---|---|
|
Number of minutes to shift task window start to prevent scheduling in the past |
Adjusts task window timing for prioritized events by shifting the start time forward to prevent scheduling tasks that appear to be in the past. - Type: Non-zero integer (in minutes)
|
|
Time (in seconds) to wait before initiating the optimization process for prioritized events |
Buffer window that allows the system to collect prioritized events before triggering optimization. - Type: Non-zero integer (in seconds 60-900)
|
|
Number of events to decide if prioritized optimization can be triggered |
Minimum number of prioritized events required before triggering optimization. - Type: Non-zero integer
|
|
Maximum number of agents to be considered for prioritized event optimization |
Limits the number of technicians sent to the optimization engine for each prioritized event. If exceeded, the job will not run and no assignments will be received.
|
|
Maximum number of tasks to be considered for prioritized event optimization |
Limits the number of tasks sent to the optimization engine for each prioritized event.If exceeded, the job will not run and no assignments will be received.
|
The following is the list of solution processing properties that are available with the Schedule Optimization plugin. To access these properties, navigate to All > System Properties > All Properties.
|
Property |
Description |
|---|---|
|
sn_schedule_optim.solution_processor_packet_size |
Packet size to group events for solution processing (task updates).Sets the packet size for grouping events in solution processing, defining the capacity of each custom queue. It aims to distribute solution processing as widely as possible across the available custom queues specified in sn_schedule_optim.solution_processor_number_of_queues."
|
|
sn_schedule_optim.map_vendor_call_types |
Controls whether a synchronous or asynchronous call type is made to the map vendor. Changing the default value of sync to async can improve performance and may result in more outbound requests.- Type: String
|
|
sn_fsm_map_integr.logging.verbosity |
Captures additional logs for troubleshooting purposes. It is used for integration calls to map providers such as Beans.ai or Google, providing detailed insights to help diagnose and resolve issues.- Type: Choice
|
|
sn_schedule_optim.qualifier_data_agent_entity_split |
Indicates how many sets of agents will be processed simultaneously in an optimization run, improving performance.- Type: Non-zero integer
|
The following is the list of queue registry properties that are available with the Schedule Optimization plugin. These properties configure parallel event and data processing queues to optimize performance for simulation and optimization runs. To access these properties, navigate to All > System Policies > Queue Registry.
|
Property |
Description |
|---|---|
|
sn_schedule_optim.data_queue |
Queue registry for Schedule Optimization data processing (GraphQL qualifier response).- Job Configuration Type: Scale with node
|
|
sn_schedule_optim.event_queue |
Queue registry for Schedule Optimization solution (event) processing.- Job Configuration Type: Scale with node
|
|
sn_schedule_optim.event_attr_queue |
Queue registry for Schedule Optimization break (event attribute) processing.- Job Configuration Type: Scale with node
|
The following system properties are available with the Predictive Intelligence plugin. To access these properties, navigate to All > System Properties > All Properties.
|
Property |
Description |
|---|---|
|
glide.platform_ml.training.retry.limit |
Controls how many times the optimization engine will retry if the machine learning service fails. Set to
|
Related topics
Configuring Schedule Optimization
--- title: Schedule Optimization properties description: You can set parameters that control how optimization runs. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/field-service-management/schedule-optimization-properties.html release: australia topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 10 breadcrumb: [Schedule Optimization components, Reference, Field Service Management] --- # Schedule Optimization properties You can set parameters that control how optimization runs. ## Field Service Schedule Optimization properties ## Schedule Optimization general properties <table id="table_dy4_zsj_21c"><thead><tr><th> Property </th><th> Description </th></tr></thead><tbody><tr><td> Exit buffer time </td><td> Amount of time \(in minutes\) to add between the end of a task and the travel start of the next. An example of a valid time value is 10.- Type: Integer - Default value: 0 - Location: **All** > **Field Service** > **Administration** > **Properties** </td></tr><tr><td> Qualifier type for schedule optimization </td><td> The qualifier type for schedule optimization determines the criteria used to optimize schedules. There are two qualifier types available: "Assignment group" and "Territory."When the Field Service Territory model is enabled, the qualifier type automatically switches to "Territory" and remains fixed. This means that when the Territory model is active, the optimization process focuses on territories instead of assignment groups. For more information, see [Enable the Field Service territory model](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/field-service-management/workforce-optimization-for-field-service/enable-territory-model.md). - Type: String - Default value: Assignment group - Location: **All** > **Field Service** > **Schedule Optimization** > **Administration** > **Properties** </td></tr><tr><td> Number of seconds used for task scheduling resolution </td><td> Specifies the acceptable interval for scheduling a task. For example, the value is set to 300 seconds. Schedule Optimization will schedule tasks and the associated travel time, such as task start, travel start, or estimated end, to the nearest 5-minute start or end time. - Type: Integer - Default value: 300 - Location: **All** > **Field Service** > **Schedule Optimization** > **Administration** > **Properties** </td></tr><tr><td> Maximum number of overlapping qualifiers in a qualifier set </td><td> Numeric value set to determine the maximum number of overlapping qualifiers that can be applied to a single qualifier set.- Type: Integer - Default value: 30 - Location: **All** > **Field Service** > **Schedule Optimization** > **Administration** > **Properties** </td></tr><tr><td> Logging level </td><td> The logging level will determine the type of information displayed in the results of an optimization log entry, providing details about the Schedule optimization run. There are four options available: Error, Warning, Info, and Debug.- Type: Choice - Default value: Error - Location: **All** > **Field Service** > **Schedule Optimization** > **Administration** > **Properties** </td></tr></tbody> </table>## Schedule Optimization travel time estimate properties <table id="table_rmt_mjt_bfc"><thead><tr><th> Property </th><th> Description </th></tr></thead><tbody><tr><td> Maximum number of location points allowed in a map vendor call </td><td> Numeric value set to determine the maximum number of location points allowed in a map provider call. Beans.AI is the map provider that Schedule Optimization supports for travel time estimates. For more information, see [Schedule Optimization travel estimate providers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/field-service-management/schedule-optimization-travel-estimate-providers.md). - Type: Integer - Default value: 300 - Location:**All** > **Field Service** > **Schedule Optimization** > **Administration** > **Properties** </td></tr></tbody> </table>## Schedule Optimization system properties The following system properties are installed with Schedule Optimization. <table id="table_hgt_tbh_5fc"><thead><tr><th> Property </th><th> Description </th></tr></thead><tbody><tr><td> sn\_schedule\_optim.so\_max\_batch\_duration </td><td> Maximum duration between start and end time on a batch run, in hours.- Type: Non-zero integer \(in hours\) - Default value: 6 - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.so\_min\_batch\_duration </td><td> Minimum duration between start and end time on a batch run, in hours.- Type: Non-zero integer \(in hours\) - Default value: 2 - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.consider\_overlapping\_territories\_for\_scheduling </td><td> Controls whether overlapping territories are considered when scheduling tasks during optimization.- Type: True/False - Default value: True - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.max\_priority\_events </td><td> Maximum number of prioritized event types that can be configured to trigger optimization.- Type: Non-zero integer - Default value: 3 - Location: System Properties list \[sys\_properties\] table **Note:** The 'maint' role is required to edit this property. This role is exclusive to internal users. Contact support to make changes. </td></tr><tr><td> sn\_schedule\_optim.intraday\_assignment\_horizon\_offset </td><td> Specifies the time offset \(in minutes\) added to the current time when calculating the window start for tasks that have no defined window start.- Type: Non-zero integer - Default value: 60 - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.intraday\_max\_retry\_count </td><td> Specifies how many times the solution processor retries submitting an intraday optimization job.- Type: Integer - Default value:1 - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.intraday\_minimum\_frequency </td><td> Defines how frequently intraday optimization runs.- Type: Non-zero integer - Default value \(in minutes\): 15 - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.intraday\_policy </td><td> Specifies the default policy for intraday optimization. This can be overridden at the group level.- Type: String - Default value: None - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.intraday\_qualifier\_type </td><td> Specifies whether intraday optimization runs by assignment group or territory.- Type: Choice list - Default value: Assignment group - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.intraday\_window </td><td> Defines the default schedule that controls when intraday optimization can run.- Type: String - Default value: None - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.max\_agent\_count </td><td> Limits the number of technicians considered during on‑demand and intraday optimization runs.- Type: Non-zero integer - Default value: 50000 - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.max\_task\_count </td><td> Limits the number of tasks considered during on‑demand and intraday optimization runs.- Type: Non-zero integer - Default value: 50000 - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.processing\_time\_per\_task </td><td> Specifies the maximum processing time, in seconds, that the optimizer can use to compute a solution.- Type: Non-zero integer - Default value: 150 - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.run\_summary\_packet\_size </td><td> Controls how many records are grouped when generating optimization run details.- Type: Non-zero integer - Default value: 10 - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.scheduled\_state\_count\_of\_task </td><td> The number of work order tasks that can be in a scheduled state before being assigned to a technician.- Type: Non-zero integer - Default value: 1 - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.schedule\_optimization\_qualifier\_type </td><td> Specifies whether schedule optimization runs by assignment group or territory.- Type: String - Default value: Assignment group - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.schedule\_state\_type </td><td> Determines how tasks are scheduled. The choices are duration or number of tasks.- Type: Choice list - Default value: Duration - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.scheduling\_resolution\_time </td><td> The number of seconds Schedule Optimization uses to round task start times, travel times, and end times.For example, a value of 60 rounds all start times, travel times, and end times to the nearest minute. A value of 300 rounds them to the nearest 5 minutes. - Type: Non-zero integer - Default value: 1 \(second\) - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.logging.verbosity </td><td> Sets the level of detail captured in Schedule Optimization logs for each run. The choices are info, debug, warn, and error.- Type: Choice list - Default value: Error - Location: System Properties list \[sys\_properties\] table **Note:** The 'maint' role is required to edit this property. This role is exclusive to internal users. Contact support to make changes. </td></tr><tr><td> sn\_schedule\_optim.so\_max\_solution\_threshold </td><td> Maximum number of ML solutions that can run simultaneously. When workload distribution is enabled with multiple jobs or multiple optimization modes run concurrently, increase this value.- Type: Non-zero integer - Default value: 3 - Location: System Properties list \[sys\_properties\] table **Note:** The 'maint' role is required to edit this property. This role is exclusive to internal users. Contact support to make changes. </td></tr><tr><td> sn\_schedule\_optim.enable\_qualifier\_split </td><td> Determines which optimization modes use split qualifiers to distribute workloads across parallel jobs. Choices: - None – No distribution; all qualifiers processed in a single job. - Only Batch – Distribute qualifiers only for batch optimization runs. - Only Intraday – Distribute qualifiers only for intraday optimization runs. - Both – Distribute qualifiers for both batch and intraday optimization runs. **Note:** Split qualifiers work with batch, intraday, and prioritized optimization but not on-demand optimization. - Type: choice - Default value:none - Location: System Properties list \[sys\_properties\] table </td></tr><tr><td> sn\_schedule\_optim.qualifier\_distribution\_splits </td><td> Number of splits to distribute qualifiers across parallel optimization jobs for each batch or intraday configuration. Higher split counts reduce processing time per job but require more ML capacity.If running multiple optimization modes simultaneously adjust `sn_schedule_optim.so_max_solution_threshold` to accommodate the total number of concurrent ML solutions needed. - Type: Integer - Default value: 1 - Location: System Properties list \[sys\_properties\] table **Note:** The 'maint' role is required to edit this property. This role is exclusive to internal users. Contact support to make changes. </td></tr><tr><td> sn\_schedule\_optim.maximum\_matrix\_size </td><td> Determines the maximum number of locations that can be queried to a third‑party map provider when computing travel estimates.- Type: Integer - Default value: 40000 - Location: System Properties list \[sys\_properties\] table </td></tr></tbody> </table>## Intraday-Prioritized The following is the list of intraday prioritized event properties that are available with the Schedule Optimization\[var.schedule-optimization\] plugin. These properties configure prioritized event buffering, event thresholds, and limits on agents and tasks to optimize performance for time-sensitive scheduling changes. To access these properties, navigate to **All** > **Schedule Optimization** > **Administration** > **Properties**. <table id="table_xhm_z3d_jkc"><thead><tr><th> Property </th><th> Description </th></tr></thead><tbody><tr><td> Number of minutes to shift task window start to prevent scheduling in the past `sn_schedule_optim.prioritized_event_assignment_horizon_offset` </td><td> Adjusts task window timing for prioritized events by shifting the start time forward to prevent scheduling tasks that appear to be in the past. - Type: Non-zero integer \(in minutes\) - Default value: 1 minute </td></tr><tr><td> Time \(in seconds\) to wait before initiating the optimization process for prioritized events `sn_schedule_optim.prioritized_optimization_delay_buffer` </td><td> Buffer window that allows the system to collect prioritized events before triggering optimization. - Type: Non-zero integer \(in seconds 60-900\) - Default value: 180 seconds \(3 minutes\) </td></tr><tr><td> Number of events to decide if prioritized optimization can be triggered `sn_schedule_optim.prioritized_min_event_count` </td><td> Minimum number of prioritized events required before triggering optimization. - Type: Non-zero integer - Default value: 5 </td></tr><tr><td> Maximum number of agents to be considered for prioritized event optimization `sn_schedule_optim.prioritized_event_max_agent_count` </td><td> Limits the number of technicians sent to the optimization engine for each prioritized event. If exceeded, the job will not run and no assignments will be received. - Type: Non-zero integer - Default value: 20 </td></tr><tr><td> Maximum number of tasks to be considered for prioritized event optimization`sn_schedule_optim.prioritized_event_max_task_count` </td><td> Limits the number of tasks sent to the optimization engine for each prioritized event.If exceeded, the job will not run and no assignments will be received. - Type: Non-zero integer - Default value: 100 </td></tr></tbody> </table>## Performance-related Schedule Optimization properties The following is the list of solution processing properties that are available with the Schedule Optimization plugin. To access these properties, navigate to **All** > **System Properties** > **All Properties**. <table id="table_iqs_ntj_21c"><thead><tr><th> Property </th><th> Description </th></tr></thead><tbody><tr><td> sn\_schedule\_optim.solution\_processor\_packet\_size </td><td> Packet size to group events for solution processing \(task updates\).Sets the packet size for grouping events in solution processing, defining the capacity of each custom queue. It aims to distribute solution processing as widely as possible across the available custom queues specified in sn\_schedule\_optim.solution\_processor\_number\_of\_queues." - Type: Integer - Default value: 10 </td></tr><tr><td> sn\_schedule\_optim.map\_vendor\_call\_types </td><td> Controls whether a synchronous or asynchronous call type is made to the map vendor. Changing the default value of sync to async can improve performance and may result in more outbound requests.- Type: String - Default value: "beans": "sync" </td></tr><tr><td> sn\_fsm\_map\_integr.logging.verbosity </td><td> Captures additional logs for troubleshooting purposes. It is used for integration calls to map providers such as Beans.ai or Google, providing detailed insights to help diagnose and resolve issues.- Type: Choice - Default value: info </td></tr><tr><td> sn\_schedule\_optim.qualifier\_data\_agent\_entity\_split </td><td> Indicates how many sets of agents will be processed simultaneously in an optimization run, improving performance.- Type: Non-zero integer - Default value: 2 </td></tr></tbody> </table>**Note:** The 'maint' role is required to edit any performance-related properties. This role is exclusive to internal users. Contact support to make changes. The following is the list of queue registry properties that are available with the Schedule Optimization plugin. These properties configure parallel event and data processing queues to optimize performance for simulation and optimization runs. To access these properties, navigate to **All** > **System Policies** > **Queue Registry**. <table id="table_a5n_g51_3kc"><thead><tr><th> Property </th><th> Description </th></tr></thead><tbody><tr><td> sn\_schedule\_optim.data\_queue </td><td> Queue registry for Schedule Optimization data processing \(GraphQL qualifier response\).- Job Configuration Type: Scale with node - Default Value: 3 </td></tr><tr><td> sn\_schedule\_optim.event\_queue </td><td> Queue registry for Schedule Optimization solution \(event\) processing.- Job Configuration Type: Scale with node - Default Value: 3 </td></tr><tr><td> sn\_schedule\_optim.event\_attr\_queue </td><td> Queue registry for Schedule Optimization break \(event attribute\) processing.- Job Configuration Type: Scale with node - Default Value: 3 </td></tr></tbody> </table>## Predictive Intelligence system properties used with Schedule Optimization The following system properties are available with the Predictive Intelligence plugin. To access these properties, navigate to **All** > **System Properties** > **All Properties**. <table id="simpletable_ihd_dl4_pkc"><thead><tr><th> Property </th><th> Description </th></tr></thead><tbody><tr><td> glide.platform\_ml.training.retry.limit </td><td> Controls how many times the optimization engine will retry if the machine learning service fails. Set to `0` to disable retries and prevent unexpected work reassignment. - Type: integer - Default value: set to 0 </td></tr></tbody> </table>**Parent Topic:**[Schedule Optimization components](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/field-service-management/schedule-optimization-components.md) **Related topics** [Configuring Schedule Optimization](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/field-service-management/field-service-scheduling/schedule-optimization-engine.md) [Optimizing technician schedules at set intervals](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/field-service-management/field-service-scheduling/optimize-your-schedules-intraday.md) [Configuring log levels for detailed optimization analysis](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/field-service-management/field-service-scheduling/configuring-log-levels-for-detailed-optimization-analysis.md)
| title | Schedule Optimization properties |
| description | You can set parameters that control how optimization runs. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/australia/field-service-management/schedule-optimization-properties.html |
| release | australia |
| topic_type | reference |
| last_updated | 2026-09-10 |
| reading_time_minutes | 10 |
| breadcrumb | Schedule Optimization componentsReferenceField Service Management |