SAP Concur incident

Compleat (TMC Services): P1

Resolved after 30 minutes, affecting Compleat (TMC Services), on March 24, 2025.

resolved Apr 14, 2025, 12:39 PM UTC

Impact as Reported: In the US2 Data Center, Concur Compleat service through the SAP Concur website was unavailable. Affected TMCs may have encountered an error when attempting to access Compleat Control. Additionally, PNRs may have not been processing as expected. Root cause: The database instance was blocking several queries from running which prevented users from being able to login and use Compleat services. The Incident Response team identified that a script was executed by the support team but had been left in an incomplete state. The script was waiting on user action to complete the query. Leaving the query incomplete caused the database to put other queries on hold until the script finishes. The support team completed the user action to remediate the issues. Corrective Actions: The following corrective actions were identified Support to work with engineering to review the results of executing database scripts and monitor production Engineering to update documentation for more guidance on what to review when executing scripts to ensure they complete successfully.

Started
Mar 24, 2025, 07:05 PM UTC
Resolved
Mar 24, 2025, 07:35 PM UTC
Duration
30m
Detected by Pingoru
Mar 24, 2025, 07:05 PM UTC

Affected components

Compleat (TMC Services)

Update timeline

  1. resolved Mar 24, 2025, 08:52 PM UTC

    In the US2 Data Center, Concur Compleat service through the SAP Concur website was unavailable. Affected TMCs may have encountered an error when attempting to access Compleat Control. Additionally, PNRs may have not been processing as expected. As the Incident Response Team (IRT) was gathering, services recovered. We have verified that service performance is stable and will now resolve this incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete.

  2. resolved Apr 14, 2025, 12:39 PM UTC

    Impact as Reported: In the US2 Data Center, Concur Compleat service through the SAP Concur website was unavailable. Affected TMCs may have encountered an error when attempting to access Compleat Control. Additionally, PNRs may have not been processing as expected. Root cause: The database instance was blocking several queries from running which prevented users from being able to login and use Compleat services. The Incident Response team identified that a script was executed by the support team but had been left in an incomplete state. The script was waiting on user action to complete the query. Leaving the query incomplete caused the database to put other queries on hold until the script finishes. The support team completed the user action to remediate the issues. Corrective Actions: The following corrective actions were identified Support to work with engineering to review the results of executing database scripts and monitor production Engineering to update documentation for more guidance on what to review when executing scripts to ensure they complete successfully.

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 →