Luscii - Priority 3: Overdue alerts are not being processed automatically – Incident details

Update: Everything is stable and we are closing this incident. Should you notice anything unexpected, please don't hesitate to let us know. Thanks again for your patience.

For a number of care pathways, we saw that overdue alerts were not being processed automatically. This concerns a limited set of care pathways and is not the broader delay from last Thursday.

We have now found the underlying cause: during an earlier change, the correct setting was not carried over properly for a number of care pathways, which is why automatic processing was not working there. This has now been structurally fixed for the affected care pathways.

The open overdue alerts will unfortunately need to be closed manually this one time, the alerts themselves can simply be processed. We will continue to monitor this closely. We apologise for the inconvenience.

Update: The automatic processing of overdue alerts unfortunately experienced problems again today. This has now been fixed and we are monitoring the situation. We will continue to keep an eye on it over the weekend.

Unfortunately, some overdue alerts that should have been processed automatically were not, these will need to be closed manually by caregivers. We apologise for this inconvenience.

The issue has been resolved. A large volume of background tasks this morning caused a delay in processing. This was most noticeable in the forwarding of alerts to the EPD (HiX), and also affected (automatic) workflows and additional measurements. Everything has now been fully processed and the alerts in HiX have caught up, no data has been lost. We have scaled up capacity and moved the tasks in question so they no longer hold up regular processing. We are also taking steps to ensure this does not happen again. Thank you for your patience.