SAP Concur incident

Expense: P1

Resolved after 5 hours 14 minutes, affecting Expense, on November 2, 2015.

investigating Nov 16, 2015, 10:49 PM UTC

Expense was intermittently unavailable. Users were unable to log in. If already logged in, users experienced errors, slow processing or were logged out when performing administrative functions, attempting to create, view, save or approve expense reports. The cause of this disruption was due to increased memory pressure leading to an unresponsive server. To resolve this issue, an index was added to a stored procedure that was running inefficiently in addition to increasing the memory footprint on the affected server. We will be releasing a code change to the affected stored procedure and closely monitoring memory usage to prevent future reoccurrence.

Started
Nov 02, 2015, 07:00 AM UTC
Resolved
Nov 02, 2015, 12:14 PM UTC
Duration
5h 14m
Detected by Pingoru
Nov 02, 2015, 07:00 AM UTC

Affected components

Expense

Update timeline

  1. investigating Nov 02, 2015, 11:38 AM UTC

    Some users may experience errors, slow processing or are logged out when attempting to create, view, save, or approve expense reports.

  2. investigating Nov 02, 2015, 12:04 PM UTC

    Users are unable to log in. If already logged in, users are experiencing errors, slow processing or are logged out when performing administrative functions, attempting to create, view, save or approve expense reports. We appreciate your patience while we work to resolve this issue.

  3. investigating Nov 02, 2015, 12:29 PM UTC

    We have resolved the issue and will provide the root cause analysis as soon as possible.

  4. investigating Nov 16, 2015, 10:49 PM UTC

    Expense was intermittently unavailable. Users were unable to log in. If already logged in, users experienced errors, slow processing or were logged out when performing administrative functions, attempting to create, view, save or approve expense reports. The cause of this disruption was due to increased memory pressure leading to an unresponsive server. To resolve this issue, an index was added to a stored procedure that was running inefficiently in addition to increasing the memory footprint on the affected server. We will be releasing a code change to the affected stored procedure and closely monitoring memory usage to prevent future reoccurrence.

Your product runs on more than SAP Concur

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →