Manage booking with scheduling model

This section outlines the administrative and diagnostics controls used to govern the background engine of the Booking module. To ensure that the Resource Time Allocation Monitor remains an accurate reflection of real-world resource availability, the system runs periodic background simulations. Through the Automatic Scheduling Calendar and Model Processing interfaces, administrators can configure automated processing rules, monitor execution metadata, and manually force optimization cycles to audit system behavior.

Access processing parameters

To see the parameters that process the model:

1. Navigate to an active scheduling model.

   • Note: This command is enabled only for models of the Booking with scheduling type.

2. In the model interface, click the Three dot menu.

3. To open the configuration interface, select Automatic Scheduling Calendar.

Define processing rules

To make rules to process your scheduling model:

1. Click New on the top of table

2. Enter the required values into the configuration fields:

   • Day: The specific day(s) of the week the process should run.

   • Interval: Defines the frequency of the launch (e.g., every X minutes).

   • Start / end: The time window during the day when the periodic task is active.

   • Process day: The time range into the future that the simulation should consider.

Check model metadata

To find metadata about your model:

1. Navigate to the Capacity saturation monitor.

2. Click the Three dots menu.

3. Select Model processing.

4. Review the metadata fields for your selected booking model:

   • Booking model description: The name and specific details of the model

   • Last processing execution date: The timestamp of the most recent run

   • Last processing interval: The exact duration of the previous execution

   • Processing status:

     • Completed

     • Running

     • Failed

   • Error: Detailed logs of any issues encountered during the last run

   • Processing period start - end: The specific time horizon covered by the last simulation

Force a manual process launch

To check if capacity is saturated:

1. In the Capacity saturation monitor, click the Model processing page.

2. To trigger an on-demand calculation, click Process.

3. Check if the system blocks execution based on the mandatory validation checks:

   • Period validation: The system verifies that the requested processing period is less than or equal to the limit defined in the parameter: company.fsm.optimization.maxPeriodBookingWithScheduling

   • Concurrency check: Same model: If an execution for the same model is already in progress, the system blocks the launch and returns a blocking error.

   • Concurrency Check: Global Queue: The system counts all active and planned Booking model processes. If the total exceeds the limit defined in the following parameter, a blocking error is returned:company.fsm.optimization.maxPlannedBookingSchedulingProcesses.

See the execution logic of scheduling task