Release notes

Optimization recipes: keep allocated Resources on Jobs
8 October 2026
Web AppSchedulers

Optimization Recipes now include a Retain allocated resources setting. When it's on, Resources already allocated to a Job stay on that Job during an optimization run, and optimization fills only the remaining allocations.
This helps teams that allocate key people to a Job up front and then use optimization to staff the rest. For example, if a Job needs five Resources and two are already allocated, optimization keeps those two and finds the other three.
What's new
- Allocated Resources stay in place: Optimization won't reassign or remove Resources already allocated to a Job.
- Remaining slots are filled: For Jobs that need more than one Resource, optimization allocates only the unfilled slots.
- Job times can still change: Optimization may move a Job's scheduled time to suit both the kept and newly allocated Resources.
- Unavailable Resources block scheduling: If a kept Resource isn't available, optimization won't schedule the Job.
The setting is off by default, so existing Recipes behave as they do today.