Assignability Analysis, redesigned visualizations and limit shifts per day within a paired employee group in ESS

Today, we're announcing version v1.12 of the Timefold Platform and updates to the Timefold models.

This new version of the Timefold Platform comes with these platform improvements:

Stop solving after a set number of moves, not just a time limit
: A new termination setting, move count limit, is now available in configuration profiles, as a dataset override when submitting a dataset, and in the comparison table. It stops solving once a fixed number of moves have been evaluated, instead of only supporting time-based limits. See Termination settings for more details.
Clearer response when a tenant can't access a model
: Calling a model administration endpoint for a model your tenant isn't allowed to use now returns
404 Not Found
, instead of
400 Bad Request
. This more accurately reflects that the model isn't available to your tenant, rather than suggesting the request itself was malformed.
Several other smaller improvements
: This release also includes several other smaller improvements and bug fixes.

Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:

Employee Shift Scheduling (v1 | Stable)

Redesigned visualizations and Efficiency X-Rays
: The visualization views have been redesigned, and the low-level validation views (By shift and By employee) now live separately from the high-level Efficiency X-Ray views in the sidebar. Every view now supports filtering: click
Filter
in the view's toolbar to drill down into a subset of the data, for example by skill, tag, priority, or contract type. See By shift, By employee, and Efficiency X-Ray for more details.
Assignability Analysis (preview)
: Assignability analysis gives you an immediate picture of how fillable your shifts are, before any optimization runs. For each unassigned shift, it calculates what share of your employees could be assigned based on hard constraints alone, treating the rest of the schedule as empty. Shifts with 0% assignability are structurally impossible to fill and will never be assigned, no matter how the Timefold model optimizes. Shifts with a low but non-zero percentage are at risk of going unassigned due to limited options. Use it to catch impossible shifts early, understand why specific shifts go unfilled, and explore what-if changes to your workforce. This is a preview feature subject to change. See Assignability analysis for more details.
New validation warning for employees defining both available and unavailable time spans
: Employees can now trigger a
WARNING
when both
availableTimeSpans
and
unavailableTimeSpans
are defined. Only one of the two should be provided, since one assumes the employee is available by default and the other assumes the employee is unavailable by default. The two cannot be reconciled into a single availability model for the same employee. See Employee availability and Input validation for more details.
Improved solve quality for alternative shifts
: Timefold can now better assign alternative shifts. Previously, moving the group's single assignment to a different alternative shift only worked if the same employee was eligible for both shifts. A new move now allows the solver to reassign a different eligible employee when relocating the assignment within the group. See alternative shifts for more details.
Support built-in period YEAR for period rules
: Period rules now support a built-in
YEAR
period type, which defines a calendar year from January 1 to December 31, with leap years automatically accounted for. This allows you to define rules that apply on a yearly basis, providing greater flexibility in scheduling and planning. All period rules now support by default: DAY, WEEK, MONTH, YEAR, SCHEDULE, MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, and SUNDAY. See Minutes worked per period for more details.
Limit shifts per day within a paired employee group (preview)
: Employee pairings with
groupByEmployeeTag
and
commonTagType
now support
groupShiftsPerDayLimit.groupShiftsPerDayMax
, capping how many different shift hours an employee group may work on the same day. Setting
groupShiftsPerDayMax: 1
requires the group to work identical shift hours whenever they share a day together, while higher values allow the group to split across that many different shift hours.
groupShiftsPerDayLimit
requires both
groupByEmployeeTag
and
commonTagType
to be set. This is a preview feature subject to change. See Limiting how many different shift hours a group can work per day for more details.

Field Service Routing (v1 | Stable)

Maintenance release updating dependencies to deliver security updates and minor performance improvements.

Pick-up and Delivery Routing (v1 | Preview)

Maintenance release updating dependencies to deliver security updates and minor performance improvements.

Please let us know if you have feedback.