Timefold
Log in
Feature Requests
Changelog
←
Back to changelog
Powered by Canny

new

improved

fixed

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Pickup & Delivery Routing

Machine-readable validation errors for FSR, weights for preferences in ESS, and more

Today, we're announcing version v1.1.0 of the Timefold Platform and updates to the Timefold models.
This new version of the Timefold Platform comes with these platform improvements:
  • Real-time updates to plans list
    : The datasets overview page in the platform now updates in real-time when new datasets are submitted or being solved.
  • Several bug fixes and stability improvements
    , including a bug that sometimes caused a Platfrom UI login loop.
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Employee Shift Scheduling (v1 | Stable)
  • Tag matching for breaks during shifts
    : By default, breaks are not counted toward hours worked. It is now possible to optionally supply tags for breaks, which specify whether breaks are counted or not towards hours worked for a certain rule. See Shift Breaks for details.
  • Disruption scope
    : Disruption rules in employee contracts now support a configurable scope, which defines which shifts are deemed disrupted. For example, you can specify that a new shift is only considered disruptive if it starts more than 30 minutes away from the original shift's start time. This helps minimize unnecessary disruption flags when small schedule adjustments are made. This is an experimental API that may change in future releases. See Scope configuration for details.
  • Multiple consecutive minutes off intervals in rolling windows
    : Rolling window rules now support a
    totalConsecutiveMinutesOffMin
    field. This works alongside
    consecutiveMinutesOffMinIntervals
    and lets you express complex rest requirements such as "either one block of 72 consecutive hours off, or multiple blocks of at least 32 hours that add up to 72 hours." See Total consecutive minutes off minimum in a rolling window for details.
Field Service Routing (v1 | Stable)
  • Machine-readable validation errors and warnings
    : A new endpoint
    GET /v1/route-plans/{id}/validation-result
    returns structured validation issues with a unique ID, a machine-readable
    code
    (for example
    VEHICLE_SHIFT_START_TIME_MISSING
    ), a severity (
    ERROR
    or
    WARNING
    ), and an optional
    detail
    object identifying the specific resource that caused the issue (such as a
    visitId
    or
    vehicleShiftId
    ). Two additional endpoints let you query all known issue types:
    GET /v1/route-plans/validation-issue-types
    and
    GET /v1/route-plans/validation-issue-types/{code}
    . See the user guide on input validation for more details.
Pick-up and Delivery Routing (v1 | Preview)
Maintenance release updating dependencies to deliver security updates.
Please let us know if you have feedback.