Resolved after 2 hours 46 minutes, affecting Expense, on August 5, 2026.
FRCA Impact as reported: A functional degradation impacted Expense Report submissions in the Concur Cloud for Public Sector Data Center. Concur Travel and Expense users intermittently encountered the following error after selecting Submit, when the Report Totals pop-up window was displayed: “Sorry, but something went wrong with this task. Try refreshing the page, or sign out and sign in again.” Closing the pop-up windows and continuing with the submission would successfully complete the poeration. Root Cause: A customer-impacting issue was introduced following an application update that depended on a data field not consistently available across all components involved in report processing. For affected users, submitting an expense report triggered a pop-up message stating: “Sorry, but something went wrong with this task. Try refreshing the page, or sign out and sign in again.” While this message incorrectly indicated that the submission had failed, the issue was limited to the application's error handling and validation workflow. In practice, users could dismiss the message and their expense reports were still submitted successfully. Initial incident response was delayed because alerts generated by synthetic monitoring were misdiagnosed as a defect in the monitoring test itself rather than an indication of a customer-facing issue. Once engineers correlated the alerts with customer behavior and confirmed the impact, the source of the issue was identified as a mismatch between newly deployed application components and a required dependency, causing the application to incorrectly generate an error message during report submission. Service was restored by rolling back the recent deployment and returning the environment to a known-good version. The root cause was a gap in dependency and deployment coordination across multiple teams and environments, which did not provide sufficient visibility to verify that prerequisite changes had been fully deployed before dependent releases were built and promoted.
Affected components
Update timeline
- resolved Aug 06, 2026, 01:08 AM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved Aug 06, 2026, 01:27 AM UTC
We have identified a functional degradation impacting Expense Report submissions in the Concur Cloud for Public Sector Data Center. Concur Travel and Expense users may intermittently encounter the following error after selecting Submit, when the Report Totals pop-up window is displayed: “Sorry, but something went wrong with this task. Try refreshing the page, or sign out and sign in again.” As a workaround, users can close the error message, then select Submit Report from the Report Totals pop-up window, followed by Accept & Continue. This approach has successfully allowed users to submit their Expense Reports. The Incident Response Team (IRT) has been engaged and is currently investigating to determine the cause of the issue. The next update will be provided within one hour or sooner as additional information becomes available.
- resolved Aug 06, 2026, 01:59 AM UTC
We identified a functional degradation impacting Expense Report submissions in the Concur Cloud for Public Sector Data Center. Concur Travel and Expense users intermittently encountered the following error after selecting Submit, when the Report Totals pop-up window was displayed: “Sorry, but something went wrong with this task. Try refreshing the page, or sign out and sign in again.” As a workaround, users were able to close the error message, then select Submit Report from the Report Totals pop-up window, followed by Accept & Continue. This approach successfully allowed users to submit their Expense Reports. Services have returned to normal operating levels. We will continue monitoring performance for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.
- resolved Aug 06, 2026, 02:10 AM UTC
We identified a functional degradation impacting Expense Report submissions in the Concur Cloud for Public Sector Data Center. Concur Travel and Expense users intermittently encountered the following error after selecting Submit, when the Report Totals pop-up window was displayed: “Sorry, but something went wrong with this task. Try refreshing the page, or sign out and sign in again.” As a workaround, users were able to close the error message, then select Submit Report from the Report Totals pop-up window, followed by Accept & Continue. This approach successfully allowed users to submit their Expense Reports. The Incident Response Team (IRT) determined that the issue was caused by a recent service update. The team reverted the update, which resolved the issue and restored normal Expense Report submission functionality. 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.
- resolved Aug 17, 2026, 08:43 AM UTC
FRCA Impact as reported: A functional degradation impacted Expense Report submissions in the Concur Cloud for Public Sector Data Center. Concur Travel and Expense users intermittently encountered the following error after selecting Submit, when the Report Totals pop-up window was displayed: “Sorry, but something went wrong with this task. Try refreshing the page, or sign out and sign in again.” Closing the pop-up windows and continuing with the submission would successfully complete the poeration. Root Cause: A customer-impacting issue was introduced following an application update that depended on a data field not consistently available across all components involved in report processing. For affected users, submitting an expense report triggered a pop-up message stating: “Sorry, but something went wrong with this task. Try refreshing the page, or sign out and sign in again.” While this message incorrectly indicated that the submission had failed, the issue was limited to the application's error handling and validation workflow. In practice, users could dismiss the message and their expense reports were still submitted successfully. Initial incident response was delayed because alerts generated by synthetic monitoring were misdiagnosed as a defect in the monitoring test itself rather than an indication of a customer-facing issue. Once engineers correlated the alerts with customer behavior and confirmed the impact, the source of the issue was identified as a mismatch between newly deployed application components and a required dependency, causing the application to incorrectly generate an error message during report submission. Service was restored by rolling back the recent deployment and returning the environment to a known-good version. The root cause was a gap in dependency and deployment coordination across multiple teams and environments, which did not provide sufficient visibility to verify that prerequisite changes had been fully deployed before dependent releases were built and promoted.
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.
Amazon Web Services