Timefold
Home
Feature Requests
Changelog

Changelog

Follow up on the latest improvements and updates.

RSS

new

improved

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Real-time planning improvements (preview: /from-patch and FSR pinning) and HMAC webhook support (v0.54.4)

Today, we’re announcing version v0.54.4 of the Timefold Platform and v1.12.0 of the Timefold models.
This new version of the Timefold Platform comes with these platform improvements:
We’re introducing a preview API endpoint for real-time replanning:
/from-patch
. This allows you to make incremental changes to an existing dataset instead of resubmitting the full dataset (for example, updating an employee’s availability, pinning a shift, adding urgent visits) while keeping traceability across versions. Each patched dataset is a new revision linked to its parent, making it easier to experiment, roll back, and analyze the impact of changes. This feature is currently available as a preview. If you’re interested in early access, please reach out to join the preview program.
You’ll see the Platform UI has been updated to reflect these new capabilities:
  • Single datasets now show the parent and origin dataset IDs.
  • A dropdown lets you easily jump between revisions of the same plan.
  • On the Plans overview, you can toggle between showing only original plans versus all revisions, including datasets created from patches.
  • We have updated the webhook configuration UI so you can now also filter on the new datasets statuses (
    DATASET_COMPUTED
    &
    DATASET_INVALID
    ) introduced in v0.53.
At the API level we have made sure that datasets created from other datasets (via
{id}/from-input
and
{id}/from-patch
endpoints) now inherit their configs from their parent, unless overridden.
Below is a screenshot of a single plan, with 4 revisions, created via
/from-patch
:
Plans & Revisions
Read the full guide on real-time planning with /from-patch (preview).
  • (Customizable) HMAC support for webhooks
    : You can now secure your webhook integrations with HMAC authorization. This verifies that requests come from the Timefold Platform and haven’t been tampered with, protecting against forged or replayed requests. By default, webhooks are signed using a standard HMAC header format (as used by many APIs), but you can also customize how signatures are calculated and sent, including using the request path or your own header names. Read the updated webhooks documentation, including HMAC examples.
  • Ability to submit plans as a reference dataset
    : You can now submit a planning problem as a static plan, without triggering further optimization. The submitted problem will still be scored and evaluated, and input and output metrics will be computed. Do this by calling the endpoints to submit planning problems with the parameter
    ?operation=NONE
    . (See API specs for details.) You can use this functionality to compare plans how they have been executed in reality with plans optimized in Timefold, or compare plans optimized by other software to plans optimized in Timefold.
  • Ability to set a default configuration profile
    : You can now set a default configuration profile for each model. This configuration profile is automatically used when creating new datasets, unless another profile is specified. Default profiles make it easier to standardize settings across datasets and ensure consistency when experimenting with different configurations. Read the configuration profile documentation.
  • Improved filtering the audit log
    : In “Tenant settings → Audit log”, you can now filter by multiple event types at once. This makes it easier to review related changes together. For example, viewing all adds, updates, and deletes for configuration profiles, or tracking multiple types of changes to Tenant Members.
  • Zooming on the score graph
    : You can now select and zoom in on a portion of the score graph to inspect that part of the solving process in more detail. This helps you spot subtle improvements or changes that may not be visible in the full view. The score graph shows how a solution’s score evolves during solving and, when hovered, displays the corresponding output metrics. This helps you understand whether the solution is still improving and what trade-offs the model is making.
  • Tags a separate column on Plans overview
    : On the Plans overview page, tags have moved to their own column, so you can now control visibility and importance of showing this in the overview via “Manage columns.”
  • Confirm tenant member delete with email
    : To avoid mistakes, we’re now asking you to confirm deletion of a tenant member by typing their email, instead of their name.
  • Several stability improvements
    .
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Field Service Routing (v1 | Stable)
  • Pinning enhancement for real-time planning
    : We’ve added finer control over which visits and shifts are pinned during real-time planning. You can now pin entire vehicle shifts or control pinning of the next visit a technician is traveling to. The model output also indicates which visits and shifts were pinned, and a new input metric “Pinned Visits” has been added. Read more.
  • Unassigned visits from visit groups in the model output
    : We have fixed the model output
    unassignedVisits
    attribute to contain also the unassigned visits from visit groups.
Employee Shift Scheduling (v1 | Stable)
  • Performance improvements
    : The model is now significantly faster and more memory efficient (by optimizing the use of constraints), delivering 2-3x quicker move calculations on typical datasets. This means you get higher quality solutions in much less time, enabling faster decision-making and improved productivity.
Please let us know if you have feedback.

new

improved

fixed

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Custom shift rotations and sequence rules for ESS, and “datasets” replace runs (v0.53.5)

Today, we’re announcing version v0.53.5 of the Timefold Platform and v1.11.3 of the Timefold models.
This new version of the Timefold Platform comes with these platform improvements:
  • Terminology update - from “runs” to “datasets”
    : We are renaming “runs” to “datasets” throughout the platform and documentation. We are doing this in preparation for new functionality coming later. (This will include the ability to easily make changes to a dataset, or comparing optimized datasets with reference datasets.) Both in the UI, in the documentation, in the OpenAPI specs of the models, and in the API responses you will see related changes. Any changes to the model API’s are backwards compatible.
  • Dataset ID improvements
    : From the overview of datasets you can now easily filter on dataset id, and on the detail page of a dataset we’ve added a quick copy-to-clipboard option.
  • Step count smart termination
    : We have added a smart termination that stops the solve operation after a predetermined amount of steps. This termination is not recommended for production use, but useful to benchmark your models, configurations and datasets. You can configure the termination via a configuration profile in the Platform UI or directly when submitting datasets.
  • Stability improvements
    : We have made several stability improvements for more graceful shutdowns and restarts when solving fails for a reason (e.g. insufficient memory). When solving fails for a reason, and needs to be restarted, we’ve fixed a problem where sometimes logs of previous solves weren’t always preserved.
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Field Service Routing (v1 | Stable)
  • Output itinerary item discriminator: We have fixed the OpenAPI spec for the OutputItineraryItem. It now contains the discriminator field. This field is either set to VISIT or BREAK depending on what the OutputItineraryItem’s `id field refers to.
  • Terminology update - from “runs” to “datasets”
    : Related to the aforementioned rename of “runs” to “datasets” a couple of changes were made to this model’s API. Check the changelog for the details. All changes are backwards compatible.
Employee Shift Scheduling (v1 | Stable)
  • Custom shift rotations
    : We have added support for defining custom shift rotations. Compared to existing weekly rotations, the custom rotations allow for flexibility in the rotation period length. This feature can help formulate rotation periods such as: “Minimum 14 days of morning, or afternoon shifts” or “Maximum 30 days of morning, or afternoon shifts”. Check the changelog for more details.
  • Sequence rules
    : We have improved capabilities of Consecutive days worked rules to support definition of shift sequences. This feature can help formulate use cases such as: “At least 2 days off after a sequence of night shifts”, “Prefer sequences of morning shifts without days off in between”, “Start a new morning or afternoon sequence on Monday”. Check the changelog for more details.
Example of shift rotations
  • Deprecation of builtInRotationPeriod in shift rotation rules
    : The
    builtInRotationPeriod
    attribute has been deprecated in favor of
    rotationPeriod
    in Shift rotation rules. See migrating from 1.10.0 to 1.11.0 for more details on required configuration changes.
  • Terminology update - from “runs” to “datasets”
    : Related to the aforementioned rename of “runs” to “datasets” a couple of changes were made to this model’s API. Check the changelog for the details. All changes are backwards compatible.
Please let us know if you have feedback.

fixed

improved

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Stability, security, and performance improvements (v0.52.0)

Today, we’re announcing version v0.52.0 of the Timefold Platform and updated Timefold models.
This release is primarily focused on strengthening the platform with:
  • Multiple bugfixes
  • Dependency updates and maintenance
  • Security upgrades
Field Service Routing (v1.10.0 | Stable)
  • Improved input validation for more robust model handling.
Employee Shift Scheduling (v1.10.0 | Stable)
  • Performance improvements for faster and more efficient scheduling runs.
Please let us know if you have feedback.

new

improved

fixed

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Technician area coverage support in FSR and various improvements (v0.51.0)

Today, we’re announcing version v0.51.0 of the Timefold Platform and v1.9.0 of the Timefold models.
This new version of the Timefold Platform comes with these platform improvements:
Benelux and Germany
  • Edit names and tags of in-progress runs
    : You can now update the names and tags of runs that are still scheduled or in progress – making it easier to classify and organize your runs.
  • Stability improvements
    : Several under-the-hood improvements for a smoother experience.
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Field Service Routing (v1 | Stable)
Employee Shift Scheduling (v1 | Stable)
  • Improved justification for “Minimize gaps between shifts”
    : The justification for the Minimize gaps between shifts for employee constraint now better reflects the actual time between consecutive shifts. See the Minimize gaps between shifts guide for details.
  • Documentation improvements
    : Added Terms & Validation guides for clarity and consistency.
Please let us know if you have feedback.

new

improved

fixed

Timefold Platform

Employee Shift Scheduling

Field Service Routing

New smarter termination, model build insights, and model improvements (v0.50.1)

Today, we’re announcing version v0.50.0 of the Timefold Platform and v1.8.0 of the Timefold models.
This new version of the Timefold Platform comes with these platform improvements:
  • Model build information in tenant settings
    : You can now view detailed build info for your models directly in tenant settings, including: Solver version, SDK version, Build commit, Build time. This helps you verify the version that is being used. (Especially useful for customers that run custom versions of models.)
  • New smart termination: “After initial solution”
    : This option stops a run immediately after the construction heuristic produces the first solution. It’s useful when you want a quick look at the initial plan before further optimization.
Screenshot 2025-09-05 at 10
  • Additionally, we’ve made several under-the-hood improvements for a smoother experience, and updated the platform documentation on inviting tenant members for clarity.
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Field Service Routing (v1 | Stable)
  • Improved scalability of movable visit handling
    : The performance of the custom move has been further optimized. Additionally, it now only activates for datasets where it brings measurable value, reducing unnecessary overhead.
Employee Shift Scheduling (v1 | Stable)
  • Disruption KPI bugfix
    : Fixed a bug where the Disruption KPI could behave incorrectly when running a score analysis on an existing run.
Please let us know if you have feedback.

new

improved

fixed

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Include unassigned visits in the output for Field Service Routing & other minor improvements (v0.49.0)

Today, we’re announcing version v0.49.0 of the Timefold Platform and v1.7.0 of the Timefold models, available on app.timefold.ai from 2025-08-25.
This release includes several minor UI improvements (including better rounding of distances in output metrics) and bugfixes (including APIs sometimes returning a faulty 500 http error) for the Timefold Platform.
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Field Service Routing (v1 | Stable)
  • Unassigned visits in the model output
    : We have added a new attribute
    unassignedVisits
    to the model output. Only the visit IDs are included in the response, not the full visit objects. See Changelog for details. This change makes the finding of unassigned visits easier and more efficient.
  • Improved scalability of movable visit handling
    : The performance of the custom move handling movable visits has been improved, especially for large datasets with many movable visits (assignable to multiple days).
  • Fixed recommendation vehicle shift dependencies
    : Fixed a bug where vehicle shift dependencies were duplicated in the output and where some vehicle shifts weren't considered as dependencies.
  • Floating breaks can be scheduled during waiting time before travel
    : Floating breaks can now be scheduled during the waiting time before travel starts, which allows for more efficient scheduling of breaks. This is especially useful for pinning. See Changelog for details.
Employee Shift Scheduling (v1 | Stable)
  • Disruption KPI
    : When submitting a schedule with already assigned employees, the
    disruption
    KPI is now always calculated. Before, this Disruption KPI was only calculated when
    disruptionRules
    were provided. See the Real-time planning feature guide for details.
Please let us know if you have feedback.

improved

fixed

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Maintenance release (v0.48.0)

Today, we’re announcing version v0.48.0 of the Timefold Platform.
This release is mostly focused on stability and protection of our platform. It introduces several bugfixes, dependency maintenance and security upgrades.
Please let us know if you have feedback.

improved

fixed

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Smaller bugfixes (v0.47.0)

Today, we’re announcing version v0.47.0 of the Timefold Platform and v1.5.0 of the Timefold models.
This release includes several UI improvements and bugfixes for the Timefold Platform, including:
  • Audit Log filters
    : Some audit log event types were missing from the filtering options. These are now correctly displayed.
  • Improved “New Run” dialog
    : We've enhanced the user experience when launching a new run for models with a large number of demo datasets.
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Field Service Routing
(v1 | Stable)
  • We’ve made several smaller performance improvements and bugfixes, e.g. to the “Visits finished in SLA” KPI’s. The UI will now better indicate when it’s an absolute value or a percentage.
  • We’ve added an improved Route optimization feature guide to our documentation.
Employee Shift Scheduling
(v1 | Stable)
  • We have updated penalties for several constraints to no longer include the shift's duration in the penalty. This change makes sure the solver does not treat shifts with different durations as more or less preferred than others. See changelog for details.
  • We have fixed a bug where two soft constraints (Preferred weekends worked per period, Preferred shift start time difference) were treated as hard constraints. See changelog for details.
Please let us know if you have feedback.

improved

fixed

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Platform shows unprocessed input file and smaller bugfixes (v0.46.0)

Today, we’re announcing version v0.46.0 of the Timefold Platform and v1.4.0 of the Timefold models.
This new version of the Timefold Platform comes with these platform improvements:
  • “Input” now showing unprocessed file
    : For any new runs, the “Input” page for a Model Run will now show the .json-file as it was submitted to the platform, without pre-processing. Before today we showed a version where default configuration values (from e.g. the configuration profile or tenant plan) were mixed in.
  • We have fixed several small UI bugs.
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Field Service Routing
(v1 | Stable)
  • Visualization bugfix: We fixed a bug with character encoding in the visualization of the model.
Employee Shift Scheduling
(v1 | Stable)
  • Visualization bugfix: We fixed a bug with character encoding in the visualization of the model.
Please let us know if you have feedback.

new

Timefold becomes ISO 27001:2022 certified (v0.45.0)

Today, we’re announcing version v0.45.0 of the Timefold Platform and v1.3.0 of the Timefold models.
With this release we’re happy to announce Timefold has become ISO 27001:2022 certified. Head over to trust.timefold.ai to learn about all of our security & compliance measures. You can use our Trust center to request the certificate & report. We are still in the process for SOC 2 compliance - expect updates on that later.
64251bc1658b1d787bf5a5d2_FTR_ISO_27001_doc
This new version of the Timefold Platform also comes with these platform improvements:
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Field Service Routing
(v1 | Stable)
  • Deprecated /run and /new-run endpoints
    : The endpoints
    GET /v1/route-plans/{id}/run
    and
    POST /v1/route-plans/{id}/new-run
    have been deprecated, and replaced. See upgrade to the latest version for details.
Employee Shift Scheduling
(v1 | Stable)
  • Working time fairness metric fix
    : We have fixed a bug that caused incorrect calculation of the Fairness metric when Full-time equivalent configuration was used in employee contracts.
  • Deprecated /run and /new-run endpoints
    : The endpoints
    GET /v1/schedules/{id}/run
    and
    POST /v1/schedules/{id}/new-run
    have been deprecated, and replaced. See upgrade to the latest version for details.
Please let us know if you have feedback.
Load More
→