Concur Support & User Guides

11 February 2026 | 12:24 pm

Impact as Reported: Some New Concur Travel customers were unable to perform successful travel searches. Our internal monitoring tools measuring successful travel submissions detected a 95% drop in travel submissions. Further investigation confirmed impact to successful travel submissions was caused by an error, "Sorry something went wrong" when attempting to perform an air, car, and hotel travel search. If you experienced impact, you may have been able to successfully perform a search by trying again Root cause: A service configuration update reducing a session timeout for a travel service connections to a central database with the intent of implementing better session management inadvertently resulted in increased session termination and creation, leading to excessive load on the target database and consequent degradation for all services connecting to it. The change was reverted to restore service to normal. Corrective Actions: The following corrective and preventive actions have been identified: The configuration change has been reverted; The pre-release testing is being revised to ensure appropriate load is applied to detect this type of potential issues.

11 February 2026 | 12:18 pm

Impact as Reported: New Concur Travel users experienced an issue completing travel bookings. Affected users may have encountered the following error when attempting to complete their travel booking from the Review and Book page, "Sorry, something went wrong." There was no workaround identified during service disruption. Root cause: A zero downtime patching operation on a vendor managed data store unexpectedly resulted in a temporary loss of connectivity resulting in degradation for services depending on it. Service returned to normal once the operation completed. The vendor has indicated that the issue likely was the result of the operation happening while the data store was under high load and has provided recommendation that are being implemented as preventative actions. Corrective Actions: The following preventative actions have been identified: The zero downtime patching process has been updated to restrict execution to low traffic times and to include validations to ensure no large workload is being processed when the operation takes place; The interval between database connection retries has been increased to reduce the chance of saturating the number of available connections.