Training
Fox World Travel Concur Support Desk
Fox World Travel is available to support your Concur questions. Contact support via phone at 608-710-4172, via email at online@foxworldtravel.com or via chat in the Concur application.
Additional Support
Contact your institution’s travel manager for additional support questions.
Personalized SAP Concur Open Updates
Personalized up-to-the-minute service availability and performance information
-
OPI-6240069 : US2 | EU2 : Travel : Root Cause Analysis
29 May 2026 | 5:33 am
Impact as Reported: All Sabre SAP Concur Travel customers experienced an issue completing travel bookings for air, hotel, car, and rail segments. Affected users encountered the following error after selecting a travel option and clicking “Book and Continue” on the Review and Book page: “An error has occurred with your booking. Start a new search and try again.” Root cause: The root cause of the incident has been identified to be a service disruption at our third party GDS partner Sabre. Corrective Actions: N/A
-
OPI-6239779 : US2 : Travel : Root Cause Analysis
29 May 2026 | 5:31 am
Impact as Reported: Approximately 85% of SAP New Concur Travel customers experienced an issue searching for air, car, hotel, or rail segments, regardless of the GDS used. Affected users may have encountered missing details on the Travel Wizard search page, or a blank page or error after submitting search criteria. In some cases, users were able to complete their search successfully after retrying. No consistent workaround was identified during the period of service degradation. Legacy Travel customers were unaffected by this incident. Root cause: The Incident Response Team identified an automated routine that was attempting to execute a large database query. This led to contention with other queries that needed to access the same dataset. The contention issue ended once the automation stopped the query having exceeded its allowed run time, and service returned to normal. Corrective Actions: The following corrective and preventative actions were identified: 1. Disabled the automation from running queries on the core database impacted until further preventative actions are implemented 2. Update automation to use an estimated row count limit to block the query from running automatically and send to the database team for manual review. 3. Restrict the hours for automation to run on core databases to non-peak hours to avoid contention during primary business hours. 4. Update the timeout configuration to be per server so that lower timeouts can be configured for larger or most critical databases