Skip to main content

Access People Planner API Patch 2026.2.2

A
Written by Alec Cowley

Overview

We are aware that you have experienced repeated instances of system instability, including periods where the service became unavailable shortly after logging in. We understand this has caused significant disruption and we sincerely apologise for the impact this has had on your operations.

Our engineering team has investigated the root cause and identified the following:

Root Cause: Certain large API calls were being processed without a timeout limit. Under high load, these requests caused CPU spikes which led to system instability and the intermittent failures you experienced.


What We Are Doing

We are deploying a hotfix to your environment as a priority to resolve this issue.

The fix: A 120-second API timeout will be applied to all API calls. This prevents runaway requests from consuming excessive resources and causing system instability.


Important: Action Required

Please be aware of the following change in behaviour following the hotfix:

⚠️ Any API request that takes longer than 120 seconds to complete will now return a timeout error.

This is most likely to affect operations that pull large volumes of data in a single request. To avoid disruption after the fix is applied, we strongly recommend:

  • Breaking large data requests into smaller batches so that each individual call completes within the 120-second window.

  • Reviewing any scheduled or automated processes that retrieve large datasets and adjusting them accordingly.

If you are unsure whether your workflows may be affected, please contact our support team and we will be happy to assist you in reviewing your data retrieval processes.

Release Timeline

  • Live Sites: 30th June 2026

Need Help?

For more details on this release or assistance with the upgrade, please reach out to your Account Manager, Customer Success Manager, or our Support department. Visit our support community at Access Support Community for more information.

Did this answer your question?