---
sourceDocument: Australia Field Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/field-service-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Field Service Management

ft:clusterId :

    - fsm

bundleId :

    - fsm

workflow :

    - Customer and Industry


---

# Multiple Jobs for large workloads

# Running Schedule Optimization jobs for large workloads {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Run Schedule Optimization as multiple jobs for large workloads.

For large workloads, Schedule Optimization runs as multiple jobs rather than one job at a time. The jobs use available ML trainers to process portions of the territories or assignment groups, reducing total processing time for large
workloads.

Batch, intraday, and prioritized optimization are supported. On‑demand optimization is not supported.  
Split qualifiers are a configuration setting that controls whether Schedule Optimization creates multiple jobs for a single run. Configure how Schedule Optimization processes large workloads by using the following system properties:

* `sn_schedule_optim.qualifier_distribution`
* `sn_schedule_optim.qualifier_distribution_splits`
{#splitting-territories-or-technicians__ul_jz4_hzt_m3c}

By default, Schedule Optimization supports three concurrent jobs. For information about adjusting this limit, see the `sn_schedule_optim.so_max_solution_threshold` property description.

For property descriptions and supported values, see [Schedule Optimization properties](https://servicenow-prod.fluidtopics.net/nOe0OO1Ywabsvcm4I0Euwg "You can set parameters that control how optimization runs.").

## When to use split qualifiers {#splitting-territories-or-technicians__section_qvt_dxr_13c}

Consider enabling split qualifiers when:

* You're optimizing large numbers of territories or work orders
* You want to process optimization workloads faster
* Your instance has ML trainer capacity available
{#splitting-territories-or-technicians__ul_rcr_2xr_13c}

## When not to use split qualifiers {#splitting-territories-or-technicians__section_e1m_kxr_13c}

Don't enable split qualifiers when:

* Workloads are small and current optimization times are acceptable
* Your instance has limited ML trainer capacity
{#splitting-territories-or-technicians__ul_hyc_qxr_13c}  
Hinweis:  
When data sets are small, splitting qualifiers may add extra processing without improving performance.

## Use cases {#splitting-territories-or-technicians__section_fb2_lyr_13c}

## Batch optimization times out before processing is finished {#splitting-territories-or-technicians__example_dyw_w1s_13c}

**Scenario:** Nightly batch optimizations for multiple territories consistently times out before completion.

**Solution:** Enable split qualifiers for batch optimization with 2-3 splits to distribute the workload across parallel jobs. Each job completes within the timeout threshold.  

## Intraday optimization performance is degrading {#splitting-territories-or-technicians__example_sjs_fbs_13c}

**Scenario:** Your intraday optimization configuration includes many qualifiers with high event volumes, causing optimization jobs to take longer than expected.

**Solution:** Enable split qualifiers for intraday optimization to distribute qualifiers across multiple parallel jobs. Each job processes fewer qualifiers and completes faster.  

## Accommodate higher processing volumes {#splitting-territories-or-technicians__example_twd_kbs_13c}

**Scenario:** Your organization expands the number of territories used, and optimization times increase beyond acceptable thresholds.

**Solution:** Enable split qualifiers for both batch and intraday optimization, incrementally increasing split count as needed to maintain acceptable optimization times.