---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Activate parallel jobs

# Activate parallel jobs for data anonymization {#ariaid-title1}

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

Use parallel jobs to reduce your anonymization job execution time.

## Vorbereitungen

Role required: admin

## Prozedur

By default data class and user based anonymization jobs run using a single thread. Multiple threads may be activated for data class and user based jobs. In addition, federated jobs used during cloning uses parallel jobs with 3 workers by default.

1. In the navigation filter enter <kbd class="ph userinput">sys_properties.list</kbd>.
2. Create the property <kbd class="ph userinput">com.glide.data_privacy.max_parallel_workers</kbd>
3. **Wahlweise:** To adjust the number of federated job parallel workers, edit the <kbd class="ph userinput">dp.max_concurrent_clone_item_workers</kbd> property.
4. Verify the Type is integer.
5. Wichtig:  
   It is recommended to start with a small number of workers per node(2 or 3).
   Enter the number of parallel job workers in the Value field up to 5.
{#parallel-jobs-anonymization__steps_ofq_kc5_dcc}