Analytics Cloud - Announcements
- 2025.10.02 - Incident Report: service disruption causing data loss
- 2025.09.30 - Release Announcement: Analytics Cloud JS v.1.3.0
- 2025.07.09 - Release Announcement: Analytics Client JS v1.1.11
- 2025.06.12 - Intermittent Service Outage - June 12th, 2025
- 2025.05.20 - Release Announcement: Analytics Client JS v1.1.1
- 2025.02.13 - Incident Report - February 6th -13th, 2025
- 2025.01.30 - Scheduled Database Migration , January 30
- 2024.10.11 - Incident Report
- 2024.08.20 - Scheduled Infrastructure Release August - 20
- 2024.08.15 - Scheduled Maintenance August - 15
- 2024.06.29 - Scheduled Maintenance June 29 - 30
- 2024.05.16 - Data Collection Disruption
- 2024.04.16 - Incident Report
- 2024.02.21 - New Feature: A/B Testing Collections
- 2023.12.05 - New Feature: Exit Pages for the Path Analysis Tool
- 2023.12.05 - New Feature: Downloading Reports
- 2023.11.01 - New Feature: Test Results for Terminated AB Tests
- 05/24/2023 to 05/26/2023 - Analytics Cloud Planned Maintenance
2024.04.16 - Incident Report
Summary
On April 16th, 2024 at 11:50AM PST, Analytic Cloud SDK 1.2.0 was released.
As part of this release, Analytics Cloud’s caching layer was updated to transition the buffering of event requests from the Local Storage API to the Cookie API. Depending on a website’s configuration and the number of requests sent on each page, the event requests buffer could grow beyond the Cookie/Request header limit allowed for most Liferay DXP installations. This resulted in invalid requests.
Thirty minutes after the 1.2.0 release, we observed issues with the release. At that point, the rollback process was immediately started. By 2:00 PM PST the SDK was successfully rolled back to the previous version.
Incident Timeline
| April 16, 11:50 AM PST | Analytics Cloud SDK 1.2.0 release |
| April 16, 2:00 PM PST | Analytics Cloud SDK 1.1.8 restore |
| April 18, 3:07 PM PST | Analytics Cloud SDK 1.1.9 hotfix release |
Impact
From April 16, 11:50 AM PST through April 16, 2:00 PM PST, visitors to some of our customer’s sites may have downloaded faulty cookies. These cookies prevented users from accessing our customer’s sites due to Invalid request errors. Unfortunately those users will continue to face Invalid Request Errors until the problematic cookies are removed.
Root cause
An unexpected cookie header size was being stored in the browser causing the DXP server to respond with invalid request status code - 400.
This issue was more likely to occur on websites that heavily use web contents for defining a page and send more than 5 simultaneous Analytics Cloud events when loading.
Mitigation Plan
Approximately 2h after the 1.2.0 release, the previous Analytics Cloud SDK was restored. Additionally, on April 18th a hotfixed version of the Analytics Cloud SDK was released with the purpose of removing the offending Cookies.
For users still observing 400 Response status code, we recommend clearing the browser's cache. This will manually remove the offending Cookies and restore access to the site. If this is not possible, please reach out to Liferay Support for further assistance.
FAQ
Has the issue been resolved?
Yes, the SDK release was rolled back and should not affect any new visitors to your site. However, customers who visited your site during the incident window may have to clear their cookies in order to access your site.
How can Liferay prevent this from happening again?
We are rethinking our approach to Cookies and will likely not use Cookies for event buffering. Additionally we are moving ahead with a canary deployment strategy to avoid any widespread issues such as this in the future.