SchemeServe incident

Agent Statements

Notice Resolved View vendor source →

SchemeServe experienced a notice incident on November 3, 2022 affecting 🎩 SchemeServe, lasting 7d 12h. The incident has been resolved; the full update timeline is below.

Started
Nov 03, 2022, 11:43 AM UTC
Resolved
Nov 10, 2022, 11:53 PM UTC
Duration
7d 12h
Detected by Pingoru
Nov 03, 2022, 11:43 AM UTC

Affected components

🎩 SchemeServe

Update timeline

  1. identified Nov 03, 2022, 11:43 AM UTC

    We are aware of an issue with running Agent Statements, which we have identified and are currently resolving. We recommend waiting until this issue is resolved before running any Agent Statements.

  2. monitoring Nov 08, 2022, 05:03 PM UTC

    A fix has been applied and we are monitoring the results.

  3. resolved Nov 10, 2022, 11:53 PM UTC

    This incident has been fully resolved, a post-mortem will follow soon

  4. postmortem Nov 11, 2022, 09:09 AM UTC

    When new cases were added to SchemeServe in certain circumstances the calculation question data from the questionset was not being correctly aggregated to the risk groups. This meant that with a recent update to the agent statement to the risk groups as opposed to just the questionset data that SchemeServe was finding cases that it did not think had been fully settled and so was including these cases on agent statement runs. This was never historically a problem and has only come to light with the update needed to agent statements to account for the new Digit accounting module. The error has now been corrected and agent statements should only include the correct cases again. Please note that SchemeServe has already contacted all clients that this may have affected and would not have caused any incorrect premiums of collected funds in any way.