---
sourceDocument: Australia Healthcare and Life Sciences
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/healthcare-life-sciences

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Healthcare and Life Sciences

ft:clusterId :

    - hcls

bundleId :

    - hcls

workflow :

    - Customer and Industry


---

# Manage high number of concurrent bookings

# Manage high number of concurrent bookings {#ariaid-title1}

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

Manage multiple parallel queues to help process mass booking appointments run in a
parallel mode. You can distribute the mass booking event processors to different nodes
rather than keeping the load on a single node.

## Vorbereitungen

Role required: sn_vaccine_sm.admin

## Warum und wann dieser Vorgang ausgeführt wird

The sn_vaccine_sm.mass_booking_parallelism property helps you implement the appointment booking flow in a parallel mode. With parallel processing, the job creates separate events for each vaccination center. It helps dispatch the events into the available parallel queues evenly. There are a total of eight mass booking event processors.  
Hinweis:  
A maximum of eight queues can be used for mass booking. Even if a user with the admin role sets the property to a value greater than 8, only eight queues are created. However, the default value is set to 4.

To avoid performance-related issues, configuration changes are required to pin to a specific node. As a user with the admin role, you can choose which thread to point to a specific node so that the load is distributed evenly
across all the nodes. For example, if you're using a multi-node instance, you can change the configuration to pin to a specific node by using the system ID field to select the specific node where you want your mass booking event
processor to hit. This configuration change can improve the system performance.

## Prozedur

1. In the navigation filter, enter <kbd class="ph userinput">sys_trigger.list</kbd>.
2. In the Search field, enter <kbd class="ph userinput">*mass booking event processor</kbd>.  
   In the Schedule table, you can see eight mass booking event processor records.
3. **Wahlweise:** If you have a multi-node instance, locate the mass booking event processor record and choose a node from the System ID column field.
4. Double-click the empty area of the System ID field.
   1. Choose a node from the list of available nodes.
   2. Save the record by clicking the green checkmark icon (![Green checkmark icon.]()‎).

   {#managing-high-number-of-concurrent-booking__substeps_pkl_kjr_v4b}  
   The mass booking event processor record is assigned to a specific node.
5. To assign different mass booking event processor records to specific nodes, repeat step 3 and step 4, as needed.