Building on Our Success: Introducing FHR 25.2

Following the successful deployment of our foundational upgrade, which saw the transition of all FHR customers to a unified FAS version, we are ready to announce our next step: the upcoming release of FHR 25.2.

FHR 25.2 is one of the two remaining planned releases set to be delivered before our Peak 2025 initiative. While this update is not a major version upgrade, it includes several important bug fixes identified since the launch of 25.1. More on this later in the article.

How will FHR 25.2 be deployed?

Thanks to the work completed in version 25.1, we are pleased to announce that FHR 25.2 will be deployed without any merchandising studio downtime for customers currently on FHR 25.1. This upgrade will take place during our regular Monday Maintenance Window, with the new version being initialised during the next full reindex that occurs overnight.

As we did with 25.1, upgrades will initially be deployed to designated test environments with the production environment being upgraded 10 business days later, on the next Monday Maintenance unless critical issues are discovered during testing.

What’s included in FHR 25.2?

The final list of features and fixes for this version is currently being finalised. FHR 25.2 will primarily focus on addressing three specific bugs identified following the release of 25.1. It will also incorporate several improvements and optimisations that were not ready in time for the previous version.

We are also planning to implement some infrastructure changes and enhancements as part of our preparations for Peak 2025. A full list of all changes will be shared shortly.

We can confirm that the following three bugs will be addressed:

1. Publishing of New Ranking Attributes: This issue can lead to a race condition in certain systems, resulting in performance degradation.
2. Copying of Campaigns: Currently, copied campaigns appear at the bottom of the list instead of the top.
3. High Volume Publishing: Publishing at high volumes (80 to 100 per hour) can cause significant performance issues.

We recommend following the Release Notes section of the knowledge base for the full release note as soon as it is made available.

Enhancing Bug Visibility

With most of our customers now using a unified version, we are proud to continue to further enhance our transparency as an organisation, in line with this effort we will introduce with FHR 25.2 a new section in our Knowledge Base dedicated to bugs identified for each FHR version. This section will feature:

• A list of known bugs associated with that version.
• Workarounds or mitigations that have been implemented or can be utilised.
• Information on which future version is expected to include fixes.

We encourage all customers to follow this section, as it will be updated frequently.

When can we expect the release of FHR 25.2?

We expect that FHR 25.2 will be available for general release late July with test environment upgrades expected to occur during the Maintenance Window on July 28th. We aim to finalise the exact date within the next week and will communicate this as soon as it is available.

What’s next?

Once we have a confirmed date for the deployment of FHR 25.2, we will notify each customer’s designated stakeholders via email with all the relevant upgrade details.

Unlike the process for 25.1, we will not be sending a proactive upgrade notification on the day of the release. Instead, all upgrade information will be communicated through the maintenance updates on our status page.

If you haven’t done so already, we encourage you to subscribe to the FHR Status Page to stay informed about all service-related communications.

Kind Regards

Product Discovery Team