Luscii - Notice history

To fix this issue permanently an maintenance window will be introduced, at 17:15 UTC our systems will be unavailable for a small window of time (expected to be approximately 20 mins) so we can roll back some infrastructure changes. After this window its expected that all issues will be resolved.

Unfortunately, the issue has returned.

The previous fix had a temporary effect, but the problem builds up over time. That’s why it seems resolved at first, but comes back later.

Because this only happens under heavy user activity, we’re unable to fully reproduce it in our test environment, which doesn’t reflect the scale of real usage.

We’re now working on a new type of approach to solve this more permanently. More updates will follow soon.

The new fix has just been deployed.

We expect this to resolve the issue completely.

We’re closely monitoring the situation to make sure everything remains stable.

Questions? Feel free to contact support@luscii.com or support@luscii.co.uk

We’ve found the cause of the issue.

• A recent change in how error messages are handled inside our system caused it to become overloaded. This triggered new errors and slowly brought the problem back.

• Because it builds up gradually, the system seemed fine at first but started failing again later.

Our team is working on a fix now. As soon as it’s ready and thoroughly tested, it will be deployed. We’ll keep you informed.

We’re seeing that the issue with loading data in Luscii has returned in some areas (web-version, HiX).

• Data doesn’t always load immediately and may show an error.

• In many cases, refreshing the page helps as workaround.
  

We understand this is inconvenient during your work. Our team is actively investigating again and working on a stable fix. Submitted measurements are still processed correctly.

The issues on the Luscii platform have now been resolved:

• Pages in the web environment and integrations sometimes didn’t load properly, this now works as expected.

• Patients sometimes saw an error when sending in measurements via the app and had to retry.

• Successfully sent measurements were correctly processed in the alert generation system. No alerts were missed on send in measurements.

Currently, there may still be a slight delay in automatic workflows and in how fast measurements appear in the app or dashboard. This is common during peak usage and recovers automatically.

A Post-Mortom will be published.

This morning Luscii had issues like slow loading and error messages. These were caused by a technical problem in the system.

A fix has now been implemented. Luscii is already performing better: pages load faster and unexpected errors are decreasing fast.

We are actively monitoring the situation.

Update: Patient creation issue: we’re working on a fix

The issue with creating new patients is caused by part of our system (ActiveMQ) being full. We are currently cleaning this up to restore normal functionality.

Other components are not affected by this issue.

If you have any questions, please contact support@luscii.com