- UpdateUpdate
The queue has now been processed. We are closely monitoring the situation and will conduct a post-mortem to evaluate the root cause and response. Once completed, we will publish our findings for transparency.
Please monitor our status page for further updates. For questions, contact us at support@luscii.com.
- MonitoringMonitoring
Half of the alerts in the queue have now been processed. We kindly ask users to refrain from making exports for the time being. We are currently receiving a large number of export requests, which is significantly slowing down the processing of alerts.
- IdentifiedIdentified
The root cause of the issue has been identified, and we have stopped the process causing it. The alerts in the queue are now being processed.
- InvestigatingInvestigating
We have identified an issue where alerts are not being forwarded to the application and are instead queued since this morning. Measurements are being received correctly. Resolving this incident is our top priority, and we are actively working on a fix.
Status:
Root cause analysis is underway.
Work is in progress.
Please monitor this status page for further updates. For questions, contact us at support@luscii.com.
- UpdateUpdate
Our developers are working on a solution for the bug. Unfortunately, the first attempt did not pass testing. Resolving this bug is technically complex. We will share an update as soon as the new solution passes testing and is published.
- IdentifiedIdentified
There is an issue where a patient performs a measurement that triggers a workflow to schedule an action. Although the action appears correctly to the patient, it is not shown in the healthcare provider’s patient schedule. This is a visual issue; the functionality is working correctly otherwise.
We are reporting this as a priority 4 issue via InStatus because Support has received several tickets about it. We do not send email notifications for priority 4 issues to avoid spamming.
Please contact support@luscii.com for further questions.
- UpdateUpdate
Occasionally, an automatic protocol switch does not go smoothly. We make manual adjustments when necessary, including outside working hours. Our developers are working on a permanent solution.
- MonitoringMonitoring
We contacted all organizations of the affected patients by the end of the afternoon. An initial fix has been implemented in the system this evening. We continue to monitor the situation closely and will apply manual corrections if necessary.
- IdentifiedIdentified
Unfortunately, we have seen that the issue has occurred more frequently. Protocol switches via alert workflows or schedules occasionally fail, affecting 0.25% of the total active patient population.
• We have classified the problem as a priority 2 critical issue.
• We will send the list of patients with the relevant protocol switches.
• If desired, we can assist with the correction. Please let us know if, and for which patients, we can still perform the switch (either at the time the switch should have occurred or now).
For further questions, please contact support@luscii.com.
- InvestigatingInvestigating
Engels: We are currently investigating a potential issue where automatic protocol changes based on protocol schedules did not occur for two protocols. We have manually transferred the patients and informed the relevant customers. Our developers are investigating the scope and root cause of the problem. Since we do not yet have a clear understanding of the scope, we are unable to fully triage the issue.
Action for healthcare providers: We kindly ask for your patience while we work to get a clearer view of the situation.
For further questions, please contact support@luscii.co.uk
Luscii Web App - Degraded performance
Luscii Web App
Luscii Android App - Operational
Luscii Android App
Luscii iOS App - Operational
Luscii iOS App
Luscii Integrations - Operational
Luscii Integrations
Luscii Metabase - Operational
Luscii Metabase
Customer portal - Operational
Customer portal