Slow Workflow Assignment

Incident Report for evalink

Resolved

During the deployment of our patch 2.15.1 there was elevated load on the workflow service - which caused longer than usual workflow creation times between 14:35 and 14:43 CET, in some cases having the operation to assign the alarm to a workflow fail. The rest of the system and alarm reception / processing wasn't affected.

This was caused by an improvement that we're doing to prevent duplicate alarm assignment in specific timings, depending on how much data some customers have it caused the assignment operation to timeout in the duplicate check.

Posted May 07, 2025 - 14:30 CEST