Timefold
Home
Feature Requests
Changelog

Changelog

Follow up on the latest improvements and updates.

RSS

new

improved

fixed

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Rolling time windows contract requirements for ESS, input metrics, and several other improvements (v0.38.0)

Today, we’re announcing version v0.38.0 of the Timefold Platform and models, including improved timeline and statuses for each model run.
This new version of the Timefold Platform comes with these platform improvements:
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Employee Shift Scheduling (v1 | Stable)
  • Support for contract requirements for rolling time windows
    : We have introduced several rolling window rules that allow you to specify both required and preferred amount of shifts, days, minutes, etc. worked over a rolling time window (instead of e.g. fixed weeks). This feature can help formulate requirements that need to be satisfied over a rolling window of time, for example: Maximum 10 Sunday shifts worked in any 52-week period, Maximum 40 hours worked in any 7-day period, Minimum 11 consecutive hours off in any 24-hour period. See “New and noteworthy” for details.
  • Days off per period in range for employees
    : We have introduced 2 new constraints for better handling of days off. This feature allows a minimum and/or maximum of days off per period to be set on contracts. See “New and noteworthy” for details.
Field Service Routing (v1 | Stable)
  • Rebalanced hard constraint weights: A missing skill or tag in an input dataset was penalized as
    -1hard
    resulting in a much smaller penalty than, for example, violating the maximum service end time of a visit. As a result, an infeasible solution that broke a skill or tag requirement was favored over an infeasible solution with all skills/tags but that didn’t finish the service in time by a couple of minutes. See “New and noteworthy” for details.
  • We have done a small bugfix to the visualization.
Please let us know if you have feedback.

new

fixed

improved

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Configurable justifications in Recommendation APIs for both models, tag exclusion filtering and several other improvements (v0.37.0)

Today, we’re announcing version v0.37.0 of the Timefold Platform and models, including improved timeline and statuses for each model run.
This new version of the Timefold Platform comes with these platform improvements:
  • Support for excluding runs with certain tags when filtering
    : When filtering the run overview, you can now choose to exclude runs with a certain tag. This gives you greater flexibility in finding and comparing certain runs. (E.g. you could label any simulation runs with a tag, and then exclude it when you want to look at only production runs.)
  • Tenant Members with expiry date
    : It’s now possible to give people temporary access to your tenant by setting an expiration date when adding/editing the members of your tenant. Use this to e.g. give our customer support team temporary access to your tenant for troubleshooting.
  • Self-hosted platforms are now single tenant
    : We’re limiting the ability for self-hosted platforms to create additional tenants. We’re doing to limit the complexity and recommend customers that self host to have multiple installations of the platform instead. More details about self-hosting the Timefold Platform versus using the Timefold Cloud Platform can be found in this comparison guide.
  • Rework of run policies
    : We have reworked the policy limiting the amount of simultaneous runs to check simultaneous threads instead. When you have e.g. 10 simultaneous threads available in your plan, you can use it to do 10 simultaneous runs each using 1 thread, or do 5 simultaneous runs each using 2 threads. We have dropped the policy that checks the maximum runs per hour.
  • We have updated the documentation to more clearly explain the different statuses of a run.
  • Smaller bugfixes (including using the configuration profile from the run when calling the score analysis API endpoint).
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Employee Shift Scheduling (v1 | Stable)
  • Configurable justifications in the Recommendations API
    : When submitting a recommendations API request, you can specify an optional boolean
    includeJustifications
    query parameter to control whether constraint match justifications should be included in the response. This is useful for getting more fine-grained information about the constraint matches, for instance to learn which period rule is violated by the recommended employee assignment. See New and noteworthy for details.
  • Priorities on Contract Rules
    : Priorities have been added to contracts. This means some contracts can now have higher priority than others. This feature allows for granular control over how much contracts comparatively weigh in solutions. It comes in handy when there is a contract that defines a certain rule that is more important than another, e.g. Contract A defines rules related to period which are more important than Contract B’s rules related to minimum time between shifts. See New and noteworthy for details.
  • Maximum number of unique tags per period per employee
    : We have introduced 2 new constraints to limit the number of unique tags that can be used to assign shifts to employees. You can use this feature to limit the amount of shift types, routes or skills that will be assigned to an employee. See New and noteworthy for details.
  • Significant speed improvements for bigger datasets
    : By pre-calculating matching rules and shifts we were able to improve the performance of datasets using global rules. We’re seeing improvements anywhere between 10% and 50%.
  • Several documentation updates, including new feature guides explaining Alternative shifts, Shift travel and locations, and Shift rules.
  • Smaller improvements (e.g. to the demo data sets) and bugfixes.
Field Service Routing (v1 | Stable)
  • Configurable justifications in the Recommendations API
    : When submitting a recommendations API request, you can specify an optional boolean includeJustifications query parameter to control whether constraint match justifications should be included in the response. This is useful for getting more fine-grained information about the constraint matches, for instance to learn which visits are not completed in time because of the recommended visit (or visit group) assignment. See New and noteworthy for details.
  • Smaller improvements (e.g. to the demo data sets and the visualization UI) and bugfixes (e.g. to the termination limit not always being respected).
Please let us know if you have feedback.

new

fixed

improved

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Improved timeline for runs, additional ESS KPIs and several other improvements (v0.36.1)

Today, we’re announcing version v0.36.0 of the Timefold Platform and models, including improved timeline and statuses for each model run.
This new version of the Timefold Platform comes with these platform improvements:
  • New “Incomplete” status and statuses visualization (breaking change)
    : We’re introducing a new status “Incomplete”, it will be used when a run ends before the construction heuristics phase of the run finished. Previously these runs were marked as successful, but the output would likely not contain all entities. With this new status users now know this is the case - we recommend setting a longer termination time when this happens. Additionally, we’ve added a timeline view of each of the different stages of a run on the Run Detail page, so it’s clearer how long each stage takes.
  • Different API calls for deletion and termination of runs (breaking change)
    : We have separated the endpoints to delete a model run from the platform, and to terminate a run in progress. Now the deletion of a run from storage is no longer done when terminating a run, but is instead done in a separate endpoint. To delete a run from the storage, the run must be in a terminated state (complete, failed or incomplete). Please refer to the OpenAPI specs of the platform for details.
  • Improved configuration profiles
    : We’ve removed the CPU setting from configuration profiles in favour of threads. We’re also indicating the maximum amount of memory per thread more clearly.
  • Change to trial process
    : We’re making a small change to the trial sign-up process - we now ask for some details about your project before approving a trial.
  • Documentation
    : We’ve added a how-to guide to explain how and why to categorize your model runs using tags.
  • Several speed improvements and bugfixes
    including a fix for timings of start and active dates when a run was restarted.
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Employee Shift Scheduling (v1 | Stable)
  • Additional KPI’s
    : We have added 4 new KPIs to provide more insights into solutions: how many employees were assigned shifts in the schedule, the number mandatory and optional shifts that were scheduled, and the total travel distance.
  • Speed improvement for global rules
    : We have improved the performance and scalability of global rules. There will be speed improvements for 9 related constraints. This improvement will result in finding solutions quicker, especially for large datasets. See New & Noteworthy for details.
  • Deprecation of required minimum
    : A minimum with a REQUIRED satisfiability is now deprecated because it may be the cause of infeasible solutions when there is a lack of shifts in the input. Use the minimum with a PREFERRED satisfiability instead. This update will result in fewer infeasible solutions when using minimums in the listed constraints. See New & Noteworthy for details.
  • Documentation
    : We’ve split up the Employee contracts feature guide into multiple guides, each explaining a separate area of functionality of the contracts feature: Period rules and Shift rules.
  • Several smaller improvements and bugfixes
    , including a fix for when shifts spanned multiple days. See New & Noteworthy for details.
Field Service Routing (v1 | Stable)
  • Several bugfixes
    including a fix for movable visit assignment (Previously, a movable visit could have blocked the assignment of another visit, resulting in the model not being able to assign all visits. A new custom move reassigns the movable visit, increasing the chance of assigning all visits.), a fix for endless loops in visit group recommendations, and fixes for the visualization of the model.
  • Documentation
    : We’ve added a new guide explaining Resource-limited planning and optional visits.
Please let us know if you have feedback.

new

improved

fixed

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Optimization gain and metric evolution in Platform and support for limited resources per location and travel configuration per employee in ESS (v0.35.0)

We’re glad to announce version v0.35.0 of the Timefold Platform and models, including a major update to the Run Details page in the Platform UI and exciting new features for Employee Shift Scheduling.
This new version of the Timefold Platform comes with these platform improvements:
  • Added optimization gain & metric evolution to Run Details page
    : We have added the optimization gain (the difference between the first and the last solution) for every metric on the Run Details page. Hover over the score graph to see the evolution of the metrics to understand the tradeoffs the software is making during optimization. See “Interpreting model run results” for more information. These changes are useful to see the real-world impact (in metrics) of the duration of solving and to understand better how different metrics impact each other (e.g. if assigned visits goes up, this also impacts technician costs and to some extent potentially overtime);
  • Showing constraints per group in Score Analysis
    : The Score Analysis overview of a run on the Run Details page now groups all constraints logically. This way you can see related constraints together to understand the model better. Our documentation site explains the features of a model per constraint group, so this way it’ll be easier to connect the features explained in the documentation to how they behave for a specific model run.
  • Export justifications
    : We have added an export button to the Run Details page that exports the justifications for a run to a
    .json
    file. You can use this to understand which constraints aren’t fully satisfied and why.
  • Improved maps documentation
    : We have improved our documentation that explains the maps service. Updates are specifically useful for customers that self-host the platform.
  • Expired trials cleanup procedure
    : Expired trials will now automatically be cleaned up when inactive. Trial users will receive an advance notification and have the option to keep their data.
  • Several smaller stability and performance improvements and minor bugfixes (including a fix for a regression when filtering on deleted runs in the Platform UI).
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Employee Shift Scheduling (v1 | Stable)
  • Allow limiting concurrent shifts per location
    : We have added the ability to control the maximum number of shifts that can take place at the same time. The feature is useful in scenarios where the shifts use a shared resource with limited capacity. See “new and noteworthy” for more details.
  • Allow travel configuration per employee
    : It is now possible to specify a list of travel configurations per contract, and not just globally. Each travel configuration can limit the distance from the home location to a shift’s location and the time between 2 shifts at different locations, within a certain time period. See “new and noteworthy” for more details.
  • Configurable rule matching behavior
    : Several types of rules (Cost Rules, Period Rules and Global Period Rules) can now be configured with more detail on when they are valid. Previously a rule’s validity period only checked a shift’s start time, but it can now be configured to also take into account the shift’s end time. See “new and noteworthy” for more details.
  • Introducing input metrics
    : The output of a model run now includes an object
    inputMetrics
    that contains the number of employees, the number of shifts and number of pinned shifts in the input dataset. (See OpenAPI Spec for a description of their meaning.)
  • We have updated our documentation for this model with several new feature guides: how to use “skills & risk factors”, how to guarantee fairness in schedules, and how to use the recommendations by the model to better handle real-time changes.
Field Service Routing (v1 | Stable)
  • Introducing input metrics
    : The output of a model run will now include an object
    inputMetrics
    that contains the number of visits, the number of visit groups, the number of vehicles, the number of mandatory visits, the number of optional visits, and number of vehicleShifts in the input dataset. (See OpenAPI Spec for a description of their meaning.)
  • Improved scalability and memory usage efficiency
    : We have improved memory usage efficiency, resulting in better scalability over datasets with large numbers of visits.
  • Added a new set of KPIs
    : The following KPIs have been added to the model output and Platform UI: the number of visits assigned, the number of mandatory visits assigned, the number of optional visits assigned, the number of vehicles used in the schedule, and the total amount of overtime required for the schedule. These new metrics will make it easier to compare different runs, e.g. when you are tweaking optimization goals. See our documentation for details.
  • We have updated our documentation for this model related to recommendations: we have added pinning in recommendations, and a visit groups recommendations guide.
Please let us know if you have feedback.

new

improved

fixed

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Configuration profiles and Shift alternatives for ESS (v0.34.0)

We’re very excited to announce this new version of the Timefold Platform, with a major new feature “Configuration Profiles”, and several updates to our models.
This new version of the Timefold Platform comes with these platform improvements:
  • Configuration Profiles
    : We’ve introduced configuration profiles for the Timefold Platform. With these profiles you can create reusable sets of constraint weights, model configuration parameters and run settings. These profiles will make it a lot easier to do goal alignment, or model benchmarking. We’ve written documentation on how you can use configuration profiles to tweak optimization goals, and how to use them for the Field Service Routing and Employee Shift Scheduling models.
  • Filtering on dates in the Model Runs Overview
    : It’s now possible to set specific date ranges when filtering on the Model Runs overview page. This should make it easier to find a specific historic run.
  • Bug fixes and improvements
    : We’ve fixed a bug where we showed certain warning messages in the layout of an error message, and where we showed an irrelevant warning about justifications. We’ve improved the handling of events that sometimes caused the status of a run to be incorrectly displayed. And we’ve upgraded the framework that the Timefold Platform is built on (Quarkus).
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Employee Shift Scheduling (v1 | Stable)
  • Shift alternatives
    : We’ve added a feature to the model that makes it possible to define a group of shifts and make sure only a specific number of them is assigned. You can use this for instance when you know a certain task needs to be done, but there’s a few options for the shift it should happen in. See New and noteworthy for more information.
  • Contractual period rules can limit logged time
    : The contractual period rules can now specify minimum and maximum logged minutes. This feature can be useful when limiting minimum/maximum shift hours that differ from the scheduled shift start to end interval, e.g. because breaks are not included in the shift working hours. See New and noteworthy for more information.
  • Documentation updates
    : We’ve made sure each of the model’s constraints now has clear descriptions. These descriptions show in the OpenAPI Specs, but also when creating a configuration profile for this model. And we have added a guide that explains metrics and optimizations goals for this model.
Field Service Routing (v1 | Stable)
  • Technician costs KPI is now optional
    : The Technician costs KPI introduced in the previous version (v0.33.0) is now only computed when a cost structure is submitted as part of the planning problem. We also have made some small improvements to the feature guide.
  • Visualization improvements
    : We’ve done some minor bugfixes to the visualization.
  • Documentation updates
    : We’ve made sure each of the model’s constraints now has clear descriptions. These descriptions show in the OpenAPI Specs, but also when creating a configuration profile for this model. And we have added a guide that explains metrics and optimizations goals for this model.
Please let us know if you have feedback.

new

improved

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Webhook improvements, FSR technician costs optimization, and more (v0.33.0)

This new version of the Timefold Platform comes with updates to these Timefold Models:
Employee Shift Scheduling (v1 | Stable)
  • Day Light Saving for Employees
    : We fixed a bug where DLS was not properly applied for employees. For more information, please see: Employee Time Zones.
  • Single-day pattern rules updates
    : We have added a custom move to facilitate matching of PREFERRED patterns. The REQUIRED single-day patterns are now deprecated and will be removed in a future version in favour of PREFERRED patterns with a high weight. More information in “New & Noteworthy”.
  • Updated model information page to more clearly reflect its features and link to relevant documentation.
  • We have added a guide explaining how to do resource-limited planning.
Field Service Routing (v1 | Stable)
  • Added technician costs optimization
    : Every vehicle shift can specify a Vehicle Shift Cost that will be used in the optimization by the minimize shift cost constraint. Please see the Technician Costs guide for details. We have added a new KPI representing the total cost of the solution and a new demo dataset that showcases the feature.
  • Recommendation calls now validate the input dataset
    : Similarly to the model run, the recommendation calls now validate the input dataset.
  • Visualization UI improvements
    : We have improved the Visualization UI, with better formatting of dates and coordinates as well as improvements to the color scheme.
  • Updated model information page to more clearly reflect its features and link to relevant documentation.
This new version of the Timefold Platform also comes with the following improvements:
Please let us know if you have feedback.

new

improved

fixed

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Fairness KPI for Field Service Routing and Visualization UI improvements (v0.32.1)

This new version of the Timefold Platform comes with updates to these Timefold Models:
Employee Shift Scheduling (v1 | Stable)
  • Visualization UI improvements
    : Shift tags are now displayed in the visualization.
  • Several smaller bugfixes.
Field Service Routing (v1 | Stable)
  • Adding a kpi for the load balancing constraint
    : We have added a new KPI for the load balancing constraint that we introduced with v0.30.0. See the feature guide for load balancing or the Timefold Platform UI for a description of its meaning.
  • Recommended Time Window alignment with visits
    : We have implemented
    minStartTime
    ,
    maxStartTime
    , and
    maxEndTime
    to replace the now deprecated
    startTime
    and
    endTime
    . Adding
    maxStartTime
    opens the possibility to get recommendations for fixed-start visits (these are visits where
    minStartTime
    equals
    maxStartTime
    ).
  • Documentation improvements
    : The feature guide explaining Lunch breaks and personal appointments was updated to include how to model “Hotel breaks”, we have added a guide explaining multi-vehicle visits and the Fairness guide has been updated to include examples and images.
  • Several smaller bugfixes.
We have also made several stability, security and performance improvements to the Timefold Platform, including better compression to save on required storage (useful for self-hosted installations) and increased performance.
Please let us know if you have feedback.

new

improved

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Multi-threaded solving for FSR, tag & name management for runs, and more (v0.31.0)

This new version of the Timefold Platform comes with updates to these Timefold Models:
Employee Shift Scheduling (v1 | Stable)
  • New metadata in the model run
    : Every run will now also have the properties
    activeDateTime
    and
    shutdownDateTime
    that keep track of when the solve-phase of a run started and stopped.
Field Service Routing (v1 | Stable)
  • Enabled multi-threaded solving
    : We have enabled multi-threaded solving for this model. Based on our benchmarking results, the maximum number of threads is limited to 4 for now. The desired maximum number of threads can be specified by the
    maxThreadCount
    attribute in Run configuration. The default is 1.
  • Visit can specify preferred vehicles
    : We have added a capability to specify preferred vehicles for a visit. When set, the visit can be assigned to a shift of one of the specified vehicles if possible. You can specify these as
    modelInput.visits[].preferredVehicles
    when submitting a new route-plan. Refer to the OpenAPI Spec for details.
  • New metadata in the model run
    : Every run will now also have the properties
    activeDateTime
    and
    shutdownDateTime
    that keep track of when the solve-phase of a run started and stopped.
This new version of the Timefold Platform also comes with the following improvements:
  • Tag & run name management via UI
    : You can now edit the name and the tags of a run via the Platform UI (after it’s finished solving). Use this to make specific runs easier to find, or to distinguish between production runs and tests or simulations.
  • New API endpoint
    POST …/{id}/new-run
    : Each model now has a new endpoint that allows you to re-run a specific dataset. The endpoint will solve the dataset again, but with the new configuration parameters you submit. This endpoint wants to make it easier to tweak configuration parameters to get to the desired result.
  • New API endpoint
    GET …/{id}/config
    : Each model now has a new endpoint that returns all the configuration parameters that were used for a specific run. You can use this endpoint to audit whether different configuration parameters had an effect on the results of different runs.
IP tracked in Audit Log: The Timefold Platform keeps an audit log for administrative actions. (The audit log is not - yet - exposed in the UI.) For safety reasons, we are now also storing the IP of the user that did the action.
docs.timefold.ai
Our documentation website has been updated with the following improvements:
  • Improved search
    : When you use the search on our documentation website, we’ll now only show results from the product you’re looking at. Previously we also suggested articles from other products, which made finding what you were looking for harder.
  • Dark/Light mode switch
    : Go to the footer of the documentation site to choose between light or dark for the documentation website. By default we’re still using the system setting, but if you prefer to override it for this specific site, now you can.
Please let us know if you have feedback.

new

improved

fixed

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Fairer distribution of work and more fine-grained control over visit priorities for FSR (v0.30.0)

This new version of the Timefold Platform comes with updates to these Timefold Models:
Employee Shift Scheduling (v1 | Stable)
Field Service Routing (v1 | Stable)
  • Fine-grained rule priorities
    : It’s now possible to define visit priorities with numbers 1 to 10 (both included). Previously only 4 priorities were supported. This allows you more fine-grained control. We are deprecating the old values, but they continue to work and have been mapped to corresponding numbers. See Upgrading to the latest versions for details and New and noteworthy for details on the 10 levels.
  • Balance work fair across technicians
    : We have added a new constraint to the model that allows you to balance the workload across technicians based on their time worked. The constraint also allows for historical data to be considered. This can be useful when you want to balance the workload based on past hours worked by the technicians. Please refer to the fairness and load balancing guide for details.
  • Visualization improvements
    : Several improvements and bugfixes were made to the visualization of planning solutions, including indications of pinned items and showing
    freezeDeparturesBeforeTime
    times.
  • Bugfix for visit time window validations: Validation for visit time windows was too strict in certain cases. This has been fixed.
This new version of the Timefold Platform also comes with the following improvements:
  • Soft Delete of Run Data
    : We now have support for restoring deleted runs for a limited amount of time. When you delete a run from your model’s run overview, they are now kept in trash for 7 days. After those 7 days the run will be permanently deleted. During those 7 days you can go to your run overview and add a filter for the property “Deleted”. If you filter on those, you can select previously deleted runs and click the Restore button.
  • Dark Mode
    : We’re launching Dark Mode on the platform. By default the UI will use your system settings, but if you prefer to override that, go to the footer of the platform to choose between light or dark.
  • Several stability and performance improvements.
Please let us know if you have feedback.

new

improved

fixed

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Tag filtering via UI, and mandatory and optional shift assignments for ESS (v0.29.0)

This new version of the Timefold Platform comes with the following improvements:
  • Tag filtering
    : Finding the run you’re looking for has just become a lot easier. When you do a run that contains a tag, the UI will now display those tags on the model run details and overview pages. Use the “Add filter” button, or click an existing tag to filter on all runs with that tag.
  • Unified error responses (including Breaking Change for API)
    : We have made sure error responses for all platform API endpoints now return the same format:
    { id: “string”, code: “string”, message: “string”, details: … }
    . While doing so we changed the
    /logs
    endpoints (like
    /v1/route-plans/{id}/logs
    ) to return a
    { details: “string” }
    object. If you depended on this endpoint, this is a breaking change.
  • Better error reporting when uploading custom files via UI
    : When you upload a custom JSON file via the Platform UI, validation errors and warnings will now be displayed in a cleaner way. We’ve moved all details to a separate dialog with the option to copy all errors and warnings as a JSON structure.
  • Improvements to trials
    : We’re now allowing newly added Tenant admins to also extend trials of models, and we’ve improved the UX when doing so.
  • Displaying maximum values for resource settings
    : When making configuration changes for a model, we’ll now display the maximum values for the resource settings (cpu’s, memory & threads), so it’s clear what range of options you have for the model’s configuration.
  • Several
    bugfixes
    (including a bug with the APIs to update environment variables for model configurations) and
    improvements
    (including loading states for models list and run details page, and opening a model’s documentation in a new tab so it’s more easily shareable and searchable).
The new version also comes with updates to these Timefold Models:
Employee Shift Scheduling (v1 | Stable)
  • Mandatory and optional shift assignment
    : We have extended shift priorities to distinguish between
    mandatory
    (default) and
    optional
    shifts. Optional shifts are useful in scenarios when conformance with a soft constraint (e.g. a
    PREFERRED
    multi-day pattern rule) is more desired than having an extra shift assigned. Learn more.
  • Multi-day pattern rules updates
    : We have added a custom move to facilitate matching of PREFERRED patterns. You may now also specify the weight of a multi-day shift pattern in the relation to the other multi-day patterns. See “Employee works preferred multi-day shift sequence pattern” rule for more information. The weight can be used to migrate from REQUIRED patterns to PREFERRED patterns with high weight, see Upgrading to the latest versions for details. Additionally we have implemented a custom move for multi-day patterns so you should see performance improvements.
  • Limit scope of “minutes between shift” rules
    : In Employee Contracts, you can specify the minimum or maximum time between shifts with
    minutesBetweenShiftsRules
    . You can now provide a scope for these rules. The scope will limit which pairs of shifts the rule is applied to. The scope excludes shift pairs where the start of the later shift is after the end of the prior shift plus the scope duration. See the updated Employee Contracts guide for examples.
Field Service Routing (v1 | Stable)
  • Improved validation and error handling when datasets contain breaks with negative durations.
  • Real-time planning documentation
    : We have added several guides explaining how to better handle day-to-day planning with scenarios that require the initial plan to change. The following scenarios are covered: a visit takes longer than expected, an urgent and unexpected visit must be added to the schedule, travel disruptions, the customer is unavailable, a technician is taken ill.
Launching a feature requests board
We’re launching a feature requests board to streamline the process of how we collect ideas and feature requests from customers like you. Please head to https://feedback.timefold.ai/feature-requests to see feature requests from others, upvote them, or add your own. When you upvote ideas, you’ll always be notified of changes to the status of the idea, including when it’s being worked on, and when ideas are implemented and made into a new version. Check “Feature requests” for a full overview of the process.
Please let us know if you have feedback.
Load More
→