Expense, Travel, Invoice, Request, Imaging, Analysis/Intelligence, Mobile: P1

Update timeline

1. resolved May 08, 2026, 06:01 PM UTC

   Some SAP Concur customers experienced a brief issue signing in to the SAP Concur website and mobile app. Users who sign in using a username and password may have seen an error message stating, “Sorry, something went wrong,” after entering their username and selecting Next. Users who were in the process of signing in during this brief service degradation may have encountered a timeout error or been redirected back to the sign‑in screen. Any user who experienced an error was able to successfully sign in by retrying. Customers using Single Sign‑On (SSO) were not impacted by this incident. The Incident Response Team (IRT) identified a recent deployment as the root cause of the issue. Service was restored once the deployment was completed. We have verified that service performance is stable and will now resolve the 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 May 21, 2026, 08:46 AM UTC

   Impact as Reported: Some SAP Concur customers experienced a brief issue signing in to the SAP Concur website and mobile app. Users who sign in using a username and password may have seen an error message stating, “Sorry, something went wrong,” after entering their username and selecting Next. Users who were in the process of signing in during this brief service degradation may have encountered a timeout error or been redirected back to the sign‑in screen. Any user who experienced an error was able to successfully sign in by retrying. Customers using Single Sign‑On (SSO) were not impacted by this incident. Root cause: During a planned updates to the authentication service, some users experienced intermittent login failures when signing in with a username and password. This occurred because the deployment was rolled out gradually, and for a short period different parts of the system were running slightly different versions of the CSRF token encryption logic. As a result, newer instances were unable to correctly process tokens generated by older ones, causing some login attempts to fail. The issue was temporary and resolved automatically once the deployment completed and all systems were running the same version. Corrective Actions: The preventative action is to identify authentication updates that may create conflicts between newer and previous versions during a rollout. Once identified, those updates will be scheduled for deployment during a maintenance window, allowing advance customer notification regarding any expected impact.