Version 0229

Updated by Leigh Hutchens

Release summary

Release date February 5 2026

Short on time and want a high-level summary?  🚀

Quinyx web app Version 0229

New functionality

  • None at this time.

New functionality requiring configuration updates

  • None at this time.

Updates and performance improvements

  • We've improved the warning titles in the filter feature for reviewing compliance issues in Base Schedule.
  • We've enhanced the Schedule filters by adding a new "Cross-unit shifts" checkbox within the Shifts grouping section.

Bug fixes

  • You might be interested in a bug fix in this release. For more information, click here.

Employee Hub Version 0229

New functionality

  • None at this time.

New functionality requiring configuration updates

  • None at this time.

Updates and performance improvements

  • None at this time.

Bug fixes

  • You might be interested in a bug fix in this release. For more information, click here.

REST API / Web service updates

  • Important update (January 30, 2026): To ensure all customers have ample time for a stable migration, the deprecation of the unpaginated Tag Categories API has been extended from February 4 to March 4, 2026 (Version 0231). Read more here.

Important information

Upcoming Webinar: Quinyx Unlocked

Join us for the February installment of Quinyx Unlocked, our monthly webinar series built exclusively for our customer community. In just 30 minutes, we’ll dive into how our latest updates simplify complex scheduling and improve your workforce planning accuracy.

  • When: February 11th at 16:00 CET (10:00 EST)
  • Duration: 30 minutes
  • Key topics: Deep dive into Absence opportunities and our Daily planning initiative (future vision)

Why attend? Gain insights into our latest tools and see where we’re headed next. You'll learn how these developments support both managers and employees, helping you maximize the Quinyx platform today and in the future.

👉 Register here!

Navigate 2026: Save the date

Navigate is back – our flagship workforce management event for customers, partners, and industry leaders.

Join us as we explore the challenges – and opportunities – shaping frontline industries, and hear directly from the people driving innovation across the sector. Navigate puts customers firmly at the centre, showcasing real-world impact, product innovation shaped by user input, and market insights that help organisations move forward with confidence.

What to expect
  • Inspiring customer stories that show what’s possible when WFM comes to life
  • A first look at product innovations shaped by customer feedback
  • Insightful discussions on the trends impacting frontline industries
  • Time to connect, learn, and exchange ideas with peers across the community
Event details
  • đź“… Date: May 6, 2026
  • 📍 Location: At Six, Stockholm — or join virtually
  • 👉 Please join us: Register here!

Updated Communication: Swedish Collective "Additional Time" Agreement Changes

We are developing a solution to support the upcoming changes in the Swedish collective agreement, ensuring continued compliance and seamless scheduling for our customers.

Our teams are actively working on the technical implementation within Quinyx. We will have this solution available by 1 April 2026, in line with the agreement change.

To support a smooth rollout, we will host dedicated training sessions in March. These sessions will provide clear, step-by-step guidance on how to configure and manage the new requirements in your environment.

We are committed to delivering this update before the agreement change date and will provide further instructions on the training schedule very soon.

Quinyx web app Version 0229

Release date February 5 2026

New functionality

None at this time.

New functionality requiring configuration updates

None at this time.

Updates and performance improvements

Base schedule warning filter improvement

We've improved the warning titles in the filter feature for reviewing compliance issues in Base Schedule. This change simplifies handling filtering violation types and speeds up the process with more descriptive names.

Cross-unit Shift visibility in Schedule filters

We've enhanced the Schedule filters by adding a new "Cross-unit shifts" checkbox within the Shifts grouping section. This improvement allows managers to toggle the visibility of shifts worked across different units, ensuring a clearer and more comprehensive overview of all employee assignments.

Bug fixes

  • Resolved an issue that caused a shift to be reassigned to the wrong employee when managers edited another employee’s shift (such as adding a task or modifying break times) due to an incorrect employee ID being sent in the update request.
  • Resolved an issue that caused nominal hours per schedule period rules to trigger incorrect hard stops when editing shifts, allowing violations when extending shifts while blocking edits that would have reduced or removed the violation.
  • Resolved an issue that prevented shifts from being updated in the schedule when sections or related shift type settings were changed in Group settings and applied using the Update shifts function.
  • Resolved an issue that incorrectly flagged breaks as being outside the shift for overnight shifts spanning midnight, even when the break time was within the scheduled shift hours.
  • Resolved an issue that caused selected variables to be cleared and statistics to reload when saving a filtered view using “Save as my view” in the schedule diagram.
  • Resolved an issue that caused shift times in the base schedule to change automatically when using the Tab key to navigate between start and end time fields.
  • New HelpDocs content

  • Mobile - Absence Opportunities
  • Quinyx Unlocked webinar videos
  • Schedule Compliance for mobile actions
  • Working with Absence Opportunities

Employee Hub web app Version 0229

Release date February 5 2026

New functionality

None at this time.

New functionality requiring configuration updates

None at this time.

Updates and performance improvements

None at this time.

Bug fixes

  • Resolved an issue that caused some comments on Stories to be cut off or hidden; users can now scroll and see all comments on a story.
  • Resolved an issue that limited widget sorting to only the "Newest first" option.

New HelpDocs content

None at this time.

REST API / Web service updates

Tag Categories API update: Deprecation postponement

We are providing an update regarding the deprecation timeline for the unpaginated Tag Categories API endpoint.

The change

The planned deprecation date for the old API endpoint, GET /categories/{categoryExternalId}/tags has been postponed.

Important update (January 30, 2026): To ensure all customers have ample time for a stable migration, the deprecation of the unpaginated Tag Categories API has been extended from February 4 to March 4, 2026 (Version 0231).

Detail

Original

Updated

Old Deprecation Date

December 10, 2025 (Release 0226)

 

Updated Deprecation Date

February 4, 2026 (Version 0229)

March 4, 2026 (Version 0231)

 

Why the Change?

This extension to the dual-run period is being implemented to provide our customers with additional time to successfully migrate their integrations to the new, performant, and paginated API (GET /v2/categories/{categoryExternalId}/tags).

We remain committed to supporting a smooth transition to the new endpoint, which resolves critical performance issues (such as 504 Gateway Timeouts and OutOfMemoryError) experienced by customers using the old endpoint with large datasets.

Action required (for users still on the old API)

Customers using the old API are strongly encouraged to complete their migration to the paginated API as soon as possible.

  • Old Endpoint (No Pagination, to be deprecated): GET /categories/{categoryExternalId}/tags
  • New Endpoint (With Pagination, required for future stability): GET /v2/categories/{categoryExternalId}/tags

The deprecation warning will be updated in our official Swagger documentation to reflect the new February 4, 2026, date.

We encourage all of our customers to make use of our APIs to maintain data and to make sure that information is up-to-date. To ensure the scalability of our APIs while growing our customer and user base, we've decided to add restrictions on the usage of our SOAP APIs. These restrictions will be enforced programmatically, which means we will enforce a limit on concurrent calls per customer to 10. You should expect response code 429 if you happen to exceed this limit, and you are recommended to implement a backoff retry mechanism to handle the limit. Note that the limit applies to SOAP only. When moving from SOAP to REST over the coming years, any limits will be built into the API. 

Please make sure to forward this information to the party within your company responsible for integrations.


How Did We Do?