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:

Real-time replanning with /from-patch (preview) and related UI updates
:

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

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.