Lonza

The incident has been solved. The issue arose after a change in the client's data. This change triggered messaging calls for heavy queries, leading to an overload of the workers. We have mitigated the situation for now and are working on a more systematic fix for later.

A short unavailability has been experienced during less than 1 minute. Our team is working on finding the root cause of this issue.

We upgraded the number of allocated instances from one to two at 09:59. The API is available again, we are investigating the root causes to

We're experiencing an issue that put the API down again. We are making actions to resolve the issue and investigate.

The incident was automatically resolved, we are investigating the root causes.

We're experiencing an issue that put the API down. We are making actions to resolve the issue and investigate.

The bug regarding Routines has been fixed, but unfortunately the correct data from that period cannot be recovered. We will assist the recovery of our customers' operations in the following way: - Providing a list of the affected Routine Executions that have invalid data. - Offering to remove the affected Routine Executions. - Rebuilding the data on Dynamic KPIs that are based on those Routines.

Due to a regression introduced by a change in the application, from Wednesday 2024-08-21 01:04 PM UTC to Thursday 2024-08-22 8:24 AM UTC, any usage of Routines resulted in invalid data being recorded. This was due to a bug that displayed incorrect Routine Steps when starting, submitting, or editing a Routine Execution; and when editing the Steps of Routines. When used during that time period, Routines were missing some Steps, or had Steps that were displayed or recorded data in an unexpected way. Therefore, the data on those Routine Executions is invalid and cannot be exploited. Dynamic KPIs based on those Routine Executions will also display incorrect data. The issue affected the Webapp, the Mobile Application, and the ability to retrieve data from Routines on our public API.

The root cause comes from a feature that was supposed to improve the loading time of images and avatars. This feature was intended to enhance the way thumbnails are managed in the legacy code. This improvement has been postponed and will be implemented in the new stack.

Service on the API is restored. We are investigating the cause of the incident.

We're experiencing an issue that put the API down. We are making actions to resolve the issue and investigate.

We are found the root cause which a specific endpoint. We will work on this endpoint to prevent future slowdowns.

The API was very slow for a short period of time, causing a congestion. We are investigating the root cause.