Optimization recipes: define behavior for jobs that are removed

Optimization recipes now let you define how jobs should be managed if they are removed from the schedule during an optimization run.

A new Job Removal section in the recipe allows you to set this behavior before running the optimization. This does not affect how the solver finds a solution; it only controls what happens to jobs that are removed from the schedule.

What’s new

You can choose what should be cleared when a job is descheduled:

• Keep job times, deallocate resources The job retains its scheduled time, but all resource allocations are removed.
• Keep resource allocation, clear job times The job keeps its resource allocations, but scheduled times are cleared.
• Clear both job times and resource allocation Both scheduled times and resource allocations are removed.

Example

A job may be removed from the schedule if keeping it would increase travel time or disrupt a logical route, allowing other jobs to be scheduled more efficiently.

This gives teams control over the state of jobs after optimization, helping maintain operational clarity and flexibility.