Guide
Splitter dry-run
The splitter dry-run is a preview execution that shows how the system would distribute waitlist requests based on the current policy and preset settings. The dry-run does not modify bookings, so you can safely test the impact of your configuration.
Running a dry-run
- Selection: choose the service or event you want to run the test for.
- Parameter check: make sure the current policy and preset settings match the expected logic.
- Start dry-run: start the run and wait for the system to generate the preview results.
Interpreting results
After the run, a detailed list shows where each waitlist request would be assigned. This preview helps you immediately see whether the distribution behaves as expected.
- Assigned bookings: which waitlist entries would receive a spot.
- Conflicts: if multiple rules apply at the same time, you can see the resulting decision here.
- Utilization: shows how much free capacity would remain.
Apply workflow
If the dry-run results look correct, you can perform the actual distribution using the Apply action. This will modify bookings and may trigger notifications, so only proceed if all results meet your expectations.
- Final review: review the list and conflicts one more time.
- Apply: start the Apply action.
- Verification: check the status of bookings and notifications.