Introducing Solve queue, saved comparison reports and Employee Efficiency X-Ray features

Today, we’re announcing version v0.62 of the Timefold Platform and updates to the Timefold models.

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

Solve queue for controlled concurrency (optional)
: We’ve introduced a new Solve queue that automatically queues solve requests when a tenant’s concurrent threads limit is reached. Instead of being rejected, datasets are accepted, and started automatically as soon as capacity becomes available. The queue is isolated per tenant, processes datasets based on priority and submission time, and can be monitored and managed via Manage tenant → Solve queue (admins can reprioritize queued runs; users have read-only visibility). By default, tenants are configured so that existing behavior does not change. If you would like to enable and start using the Solve queue for your tenant, please reach out to us. Read the Solve queue documentation.
Command palette for faster navigation
: You can now use the Command Palette to quickly navigate through the platform. Press CMD+K (or Ctrl+K on Windows/Linux) to open the palette and jump directly to specific sections of the app without manually browsing through menus.
Saved comparisons (preview)
: If you’re part of the comparison preview program, you can now save comparisons to revisit or share later. Previously, comparisons were temporary; you can now persist the selected datasets and full comparison configuration, name and describe the comparison for clarity, and choose whether it remains private or is shared with your team. See the Comparison UI documentation for more details.
Patch existing datasets via the UI (preview)
: You can now submit patches to existing datasets directly from the UI, powered by the
/from-patch
endpoint. This allows you to apply incremental changes without resubmitting the full dataset before re-solving. The /from-patch endpoint is currently in preview and only available to users enrolled in the preview program. See the /from-patch documentation for details.
Several smaller improvements and bugfixes
, including a fix when submitting tags to the
/from-input
API endpoint, and renaming "Tenant settings” to “Manage tenant” in the UI.

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

Field Service Routing (v1 | Stable)

Direct links from OpenAPI spec to feature guides
: To make it easier to move from what a property does to how and why to use it, the OpenAPI specification and UI now include direct links to the relevant feature guide documentation for key scheduling properties. This helps you transition seamlessly from the technical specification to practical guidance, examples, and best practices when configuring your model.
Vehicle-level output metrics added for better utilization insights
: In addition to the existing top-level plan metrics, the model now provides vehicle-level output metrics. This makes it easier to analyze and compare vehicle utilization (over- and under-utilization) within a plan. See Changelog for more details.
Improved error messages
e.g. when requesting recommendations for a visit that is assigned, or for locations outside of the configured map.
Auto-select as default map
: The standard configuration profile for this model now uses “Auto-select” for maps.

Employee Shift Scheduling (v1 | Stable)

New high-level efficiency visualizations (preview)
: We’ve introduced two new preview visualizations: Shift efficiency and Employee efficiency. These views extend the existing detailed schedule views with high-level validation and bottleneck detection capabilities. Shift efficiency helps identify structural coverage gaps by visualizing unassigned shifts across hours of the day and days of the week, with filtering by skill, tag, and priority, while Employee efficiency provides aggregated workforce KPIs such as deployment, overtime, preference satisfaction, and unpreference violations, including distribution charts and grouping options to detect underutilization, overload, and fairness imbalances across skills, contracts, or risk factors. Read the Visualizations documentation for more details, and if you would like to get access to these preview visualizations, please reach out to us

New shift group aware input metrics
: We have added new input metrics to distinguish between standalone shifts and shift groups. Use these metrics to understand the composition of the input data, particularly when combining standalone shifts and shift groups where multiple shifts represent alternatives and only one should be assigned. See Changelog for more details. The new metrics are only available when shift groups are used in the input dataset.
Minimize overall schedule cost documentation
: We have added a new section in the cost management guide that describes how to configure the model to minimize the overall cost of the schedule. This is useful when the goal is to minimize labor costs rather than staying within a specific budget range.
OpenAPI client generation fix
: We have fixed issues in the rotation periods schema that caused problems when generating clients from the OpenAPI specification.
Activation cost removed from global cost rules calculation
: We have removed the
employeeActivationCost
from the cost rules total cost calculation. Previously, the activation cost was incorrectly added to every shift assigned to an employee, rather than being applied as a one-time cost when the employee is first activated. The
employeeActivationCost
continues to work through the Minimize employee activation cost constraint. See migrating from 1.19.0 to 1.20.0 for migration details in case you used a combination of cost rules and employee activation cost.
Direct links from OpenAPI spec to feature guides
: To make it easier to move from what a property does to how and why to use it, the OpenAPI specification and UI now include direct links to the relevant feature guide documentation for key scheduling properties. This helps you transition seamlessly from the technical specification to practical guidance, examples, and best practices when configuring your model.
Minimize activated employees demo data renamed
: We have renamed the
MINIMIZE_ACTIVATED_EMPLOYEES
demo data to
MINIMIZE_ACTIVATED_EMPLOYEES_AND_REDUCE_COSTS
to better reflect its purpose. See migrating from 1.19.0 to 1.20.0 for more details.
Several documentation improvements
, including how to configure which days are considered weekend days and better demo data descriptions.

Pick-up & Delivery Routing (v1 | Preview)

Direct links from OpenAPI spec to feature guides
: To make it easier to move from what a property does to how and why to use it, the OpenAPI specification and UI now include direct links to the relevant feature guide documentation for key scheduling properties. This helps you transition seamlessly from the technical specification to practical guidance, examples, and best practices when configuring your model.
Auto-select as default map
: The standard configuration profile for this model now uses “Auto-select” for maps.

Please let us know if you have feedback.