Concur Support & User Guides

13 April 2026 | 10:55 am

Impact as Reported: In the US2 Data Center, some SAP Concur Expense customers experienced issues creating expense reports. Internal performance metrics indicated at least a 75% drop in expense report submissions, while internal testing confirmed affected users encountered various errors and latency within the expense report creation process or when attempting to access existing expense reports. Internal testing also showed that attempting to refresh or retry after receiving an error resulted in no changed behavior. As a workaround, affected users could sign-in to the SAP Concur mobile app to create and submit expense reports. Root cause: Some core services were experiencing performance degradation under load causing several container pods to restart. The Incident Response Team increased the pods available to handle the additional load until the service became responsive again and restored the application. In the root cause investigation, engineering identified an update to a service component unexpectedly and excessively increased resource utilization. A change was made to the component to reduce its memory usage and the updated version was deployed to production. The Incident Response Team was able to confirm that the update resolved the high load on core services and made it more responsive to requests. Corrective Actions: The following corrective and preventive actions were identified: -Updated the dependency with a more performant method to reduce resource utilization. -Update monitoring based on the metrics identified in the root cause investigation. -Update the auto-scaler to include additional metrics to ensure enough pods are available to handle traffic.

9 April 2026 | 1:14 am

Impact as Reported: In the US2 Data Center, New Concur Travel bookings were 30% below expected level. Affected users may have experienced latency and performance issues. when accessing the travel page and attempting to perform booking related tasks. Root cause: Due to resource throttling available CPU was increased on a container custer to maintain performance. However, with average CPU usage having been lowered, the containers automatically scaled down to the configured minimum number of pods, which was not sufficient to handle incoming traffic. The Incident Response team increased the number of pods to fully restore the service. Corrective Actions: The following corrective and preventative actions were identified: Additional metrics are being configure as auto-scaling triggers to maintain the optimal number of pods Monitoring is being updated to alert when pods scale down to minimum