Changelog
Follow up on the latest improvements and updates.
RSS
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.
- Deprecation of builtInRotationPeriod in shift rotation rules: ThebuiltInRotationPeriodattribute has been deprecated in favor ofrotationPeriodin 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:
- New Benelux + Germany map: A new map covering Belgium, the Netherlands, Luxembourg, and Germany is now available.
- 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)
- Technician area coverage support: A new hard constraint allows you to define the geographic area a technician can cover during their shift. See technician area coverage guide for details.
- Documentation improvements: Added Terms & Validation guides for clarity and consistency.
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.
- 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 attributeunassignedVisitsto 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, thedisruptionKPI is now always calculated. Before, this Disruption KPI was only calculated whendisruptionRuleswere 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.
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.
This new version of the Timefold Platform also comes with these platform improvements:
- Support for external map providers for the Cloud platform: We now also support connecting external map providers to tenant on the Timefold Cloud Platform, not only on self-hosted installations. Learn more about external map providers. We have also made sure any configuration changes to location sets, maps deployments and external providers are logged to the Audit Log.
- Ability to plan routing problems spanning the full US: We now have a map in production spanning the full United States. View all available maps. (We still recommend people to pick the map with the smallest fitting region, as it will speed up the solving process.)
- We have improved our documentation on the lifecycle of runs in the platform to a.o. clarify what happens if a run is cancelled, and when webhooks are triggered.
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 endpointsGET /v1/route-plans/{id}/runandPOST /v1/route-plans/{id}/new-runhave 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 endpointsGET /v1/schedules/{id}/runandPOST /v1/schedules/{id}/new-runhave been deprecated, and replaced. See upgrade to the latest version for details.
Please let us know if you have feedback.
new
improved
fixed
Timefold Platform
Employee Shift Scheduling
Field Service Routing
Improved invites, EU AI Act transparency and travel time constraints (v0.44.2)
Today, we’re announcing version v0.44.2 of the Timefold Platform and v1.2.0 of the Timefold models.
This new version of the Timefold Platform comes with these platform improvements:
- Improved member invite flows: When you invite colleagues to your tenant, they will now receive an invite email they must accept. This adds an extra layer of verification and clarity in onboarding.
- EU AI Act compliance documentation: We've published a new document detailing how Timefold complies with the EU AI Act. It highlights our transparent, deterministic approach and explains what this means for users.
- UI improvements and bugfixes: We've made several minor enhancements to the user interface (such as improving how you manage visible columns in the Run Overview) and fixed various bugs.
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Field Service Routing
(v1 | Stable)- New travel time constraints: You can now define constraints to limit the travel time of a vehicle shift, reflecting a technician’s preferences or requirements. Learn more in the Route optimization guide.
- Floating break bugfix: Fixed an issue where floating breaks ending after their maxEndTime were not correctly penalized. More details.
Employee Shift Scheduling
(v1 | Stable)- Minutes between shifts fix: We have fixed a bug that caused the constraints to ignore the minutes between shifts rule in some cases. More details.
Please let us know if you have feedback.
Load More
→