Is Locomote Down Right Now? Check if there is a current outage ongoing.

We apologise for any disruption this caused by our recent partial outage, which affected workflow and report loading. The root cause of the issue was preparatory work recently put in place for planned future upgrades, which revealed a configuration mismatch between our production and development/test environments that allowed this issue to bypass both manual and automated testing. We’ve since adjusted our test environments to align with the production configuration in question, and confirmed the issue is now correctly caught in automated tests. We are confident this class of problem is now remediated.

Reporting auth issue is now also resolved, we are monitoring for any further issues.

Reporting auth issue is now also resolved, we are monitoring for any further issues.

Workflow loading issue has been resolved. We're investigating a secondary issue with reporting access for admins.

The issue has been identified and a fix is being worked on.

3rd party has restored availability.

We've escalated and are awaiting a 3rd party API provider to resolve the issue.

This morning engineers identified and resolved an issue with the removal of a downstream system within the Management Platform. The Management Platform has been rolled back and has now resumed normal function. We apologise for the inconvenience caused by this outage. ## Issue detail Locomote has extensive test coverage of our entire application that is the cornerstone of our development confidence. The root cause of this bug slipped past detection in our test suite due to three separate issues aligning: * The cause of the bug was in code that we were deprecating ahead of future removal * The deprecation caused a false positive in a code quality tool, advising a parameter was no longer used at definition site * The removal of the parameter did not flag any test failures, because this specific code only runs in production The net result was that because the code quality tool didn’t account for call-site usage, whenever this codepath was invoked in production the parameter length now mis-matched, causing an exception. This exception was unhandled in this specific case, causing a 503 error for users accessing pages triggering this, most notably workflows. The nature of this particular change \(a deprecation\) didn’t invoke a need for production context testing, as we might otherwise do with specific production-dependent features. Our Engineering team made the choice to roll-back this particular deployment to resolve the issue as quickly as possible, and to give us time to further investigate and test the issue resolution before any future deployments. ## Remediation actions * We’re assessing our codebases for any further environment-dependent code to place extra review flags on changes in those contexts * We’re re-evaluating our out-of-hours escalation process to ensure on-call escalations happen correctly and promptly ‌ - Mario CTO Locomote

This morning engineers identified and resolved an issue with the removal of a downstream 3rd party logging system within the Management Platform. The Management Platform has been rolled back and has now resumed normal function.

Workflows should now be functioning as normal again.

We've identified the cause of workflow loading errors and are rolling out a fix.

We've received reports of workflow loading failures and are investigating.

System availability is stable, we continue to monitor and assess root cause.

We've recovered availability but are still determining root cause.

We are currently investigating this issue.

Today the Locomote platform experienced a service interruption due to an SSL certificate expiring. During the outage, users received an "Invalid SSL Certificate" error when accessing the Locomote platform from their web browser. The tech team resolved the issue promptly and will ensure it does not reoccur in the future. We want to apologise for any inconvenience caused.

Issue resolved, post-mortem notes to follow.

Issue resolved, post-mortem notes to follow.

We are continuing to investigate this issue.

After monitoring for an extended period of time, we believe the issue with our partner (Travelport) has been resolved.

Travelport have made some config changes at the core that we believe will resolve our immediate issue. We are actively monitoring current performance.

Some bookings are affected due to this issue with the Travelport Profile system. Unfortunately out of our control but we are working closely with our partners to ensure this is resolved ASAP. Affecting profile updates more severely in cases. Again if you are having issues please do jump on Live chat / contact support and our team will be there to help.

Currently our global distribution system Travelport are experiencing profile outages affecting Locomote customers. Case has been raised with Travelport and highest priority given. This is affecting some users updating profiles and completing some bookings. Please use live chat if you are experiencing any difficulties and we'll be able to support.

Hotel results are now being returned. We apologise for any inconvenience this caused. If there are any further issues please report them to our Support team by emailing support@locomote.com

Hotel results are now being returned, we are monitoring and will resolve shortly.

28 October 2019 11:00am (AEDT): We are aware of an issue where there are no hotels being returned. This has been escalated to Travelport as a priority.

This incident has been resolved.

We are aware of an issue where some users may not be able to book Jetstar (JQ) instant purchase airfares and are receiving a payment error. You can however book Jetstar (JQ) airfares with Baggage. Our team is working to resolve this as soon as possible. We apologise for any inconvenience.

The issue in which travellers were unable to book a hotel with flights has been Resolved. You will now be able to successfully book Flights, Hotels and Cars in the same booking.. We sincerely apologise for any inconvenience that this may have caused.

The issue has been identified and a fix is being implemented.

We are aware of an issue where some users may not be able to book a hotel with flights (when using On Account as payment) in the same trip. You can however book a hotel separate to the flights. Our team is working to resolve this as soon as possible. We sincerely apologise for any inconvenience.

The issue where some users may not be able to search or complete an online booking on the Locomote Corporate Travel Platform when using the latest mobile version of Google Chrome has been resolved.

We are still working on resolving the issue where some users may not be able to search or complete an online booking on the Locomote Corporate Travel Platform when using the latest mobile version of Google Chrome. If you are experiencing issues, if possible please use the desktop version, another browser on your phone (eg. Safari for iOS, Firefox for Android) otherwise you can complete an offline booking. We apologise for any inconvenience.

We are aware of an issue where some users may not be able to search or complete an online booking on the Locomote Corporate Travel Platform when using the latest mobile version of Google Chrome. Our team is currently working on a fix to resolve this as soon as possible. If you are experiencing issues, if possible please use the desktop version, another browser on your phone (eg. Safari for iOS, Firefox for Android) otherwise you can complete an offline booking. We apologise for any inconvenience.

The issue in which travellers were unable to progress past the checkout due to an error “Error unmarshalling message body: Expected” has now be Resolved. You should be able to select seats at checkout as normal. We sincerely apologise for any inconvenience that this may have caused.

We are continuing to investigate an issue on the Locomote Corporate Travel Platform in which travellers are unable to progress past the checkout page, after selecting a seat. The traveller will receive an error message stating “Error unmarshalling message body: Expected.” We advise that customers should contact their Travel Management Company if they require specific seat selection in the interim, or to book without seat selection in order to complete any bookings. We apologise for any inconvenience that this will cause and we will continue to update users with the outcome.

Locomote is aware of and is currently investigating an issue in which travellers are unable to progress past the check out page in order to complete their bookings. The traveller will receive an error message stating “Error unmarshalling message body: Expected” We advise that customers should contact their Travel Management Company in order to complete any bookings. We apologise for any inconvenience that this will cause and will continue to update users with the outcome.

We have now fixed an issue where some users were not able to reset their password to the Locomote Corporate Travel Platform when using a web browser other than Internet Explorer. This was due to CAPTCHA not properly loading, which is required to validate the password reset. We sincerely apologise for any inconvenience this may have caused.

We are aware of an issue where some users may not be able to reset their password to the Locomote Corporate Travel Platform when using a web browser other than Internet Explorer. This is due to CAPTCHA not properly loading, which is required to validate the password reset. If you need to book a trip on Locomote in the interim, then please contact your Travel Arranger or Company Administrator to book on your behalf. Our team is working to resolve this as soon as possible. We sincerely apologise for any inconvenience.

We have resolved the outage where users may not have been able to access and login to the Locomote Corporate Travel Platform. This was due to a background maintenance job that slowed the system down. We apologise for any inconvenience this may have caused.

We are aware of an issue where users may not be able access and login to the Locomote Corporate Travel Platform. We are currently investigating and are working to resolve this outage as soon as possible. We apologise for any inconvenience and appreciate your understanding.

The issue where users were unable to complete travel bookings via the Locomote platform has now been resolved. We apologise for any inconvenience that this may have caused.

We are aware of an issue in which users are currently unable to complete travel bookings via the Locomote platform. Our team is working on a fix to resolve this as soon as possible. At this stage, we strongly suggest that users book offline via their Travel Management Company. We will continue to communicate any updates moving forward. We apologise for the inconvenience that this has caused

The issues around our Support & Help Centre provider Zendesk have been resolved. You should now be unable to view, update or lodge tickets either directly via email or via our Locomote Help Centre. We apologise for any inconvenience this may have caused.

Our Support & Help Centre provider Zendesk is currently experiencing issues. During this time, you will be unable to view, update or lodge tickets either directly via email or via our Locomote Help Centre. From Zendesk: "Amazon AWS is reporting issues with their Relational Database Service affecting Support, Talk and Guide services on pod 15. We are working with them to resolve the issue. We will post more information as it becomes available." We direct you to use our chat platform Intercom for any issues, which is located on our Locomote platform. Our team will be available to answer any queries you may have. We apologise for any inconvenience.

The issue where some users may not be able to login to the Locomote Corporate Travel Platform when using Safari has now been resolved. We apologise for any inconvenience this may have caused.

We are aware of an issue where some users may not be able to login to the Locomote Corporate Travel Platform when using Safari. We have identified the cause and our team is currently working on a fix to resolve this as soon as possible. If you are experiencing issues, please use another browser (eg. Google Chrome, Firefox). We apologise for any inconvenience.

We have now resolved the issue in the Locomote platform in which users were unable to complete updates to their profile, resulting in an inability to access online workflows to book and/or arrange travel on behalf of other travellers. We apologise for any inconvenience this may have caused during this time.

We are aware of an issue in the Locomote platform in which users users are unable to complete updates to their profile, resulting in an inability to access online workflows to book and/or arrange travel on behalf of other travellers. Users may notice an error message when hovering over their online workflows, with instructions to contact Support. Users can still book/arrange travel by completing their request using an offline workflow via their travel consultant. We are currently working on fixing this as soon as possible and will update this message as we have more information. Please accept our sincerest apologies for any inconvenience caused.

The issue in which "Alternative Title" was affecting the availability of workflows for users, has been successfully resolved. You will still see the Alternative Title field within a profile, however this is now no longer mandatory unless your company configuration enforces it. Again we apologies for any inconvenience this has caused in the interim.

We have now identified the root cause where Locomote users may find that their workflows are unavailable to be selected. This was due to the "Alternative Title" section of profiles being marked as mandatory. A current workaround is to update your "Alternative Title" section of your profile to either Mr, Mrs or Miss, which will allow you to progress with bookings. A fix is being developed, that we hope to release to production as soon as possible to resolve this issue. Please accept our apologies for the inconvenience.

We are continuing to investigate this issue.

We are aware of an issue in which Locomote users may find that their workflows are unavailable to be selected. This is due to the "Alternative Title" section of profiles being marked as mandatory. A current workaround is to update your "Alternative Title" section of your profile to either Mr, Mrs or Miss, which will allow you to progress with bookings. We are working to resolve this as soon as possible. Please accept our apologies for the inconvenience.

All users are now able to fully utilise the messaging functionality with the Locomote platform without delays. If you have any further issues please contact Locomote Support. We appreciate your patience and understanding during this time.

We are continuing to investigate this issue.

We are aware of an issue in which replying to "New Message" email notifications from your email client will result in extended delays in delivery. A workaround is to reply directly from the Locomote platform via the "Messages" module. We are working to resolve this as soon as possible. Please accept our apologies for the inconvenience.

All users should now be able to load Locomote Booking tool using Internet Explorer 11. If you have any further issues please contact Locomote Support. We appreciate your patience and understanding during this time.

We have identified the issue affecting users using Internet Explorer 11 from loading Locomote booking tool. We'll advise an ETA for resolution as soon as possible.

We are aware that some users are unable to access to the Locomote Corporate Booking Tool using IE 11. We are currently investigating and will provide an update as we learn more.

All users should now be able to login to the Locomote Booking tool. If you have any further issues please contact Locomote Support. Thank you for your patience and understanding during this time.

We have identified the issue affecting some users from logging into the Locomote booking tool. We'll advise an ETA for resolution as soon as possible.

We are aware that some users are unable to login to the Locomote booking tool. We are currently investigating and will provide an update as we learn more.

We have successfully located and rectified the issue around users being unable to log into the Locomote platform. We apologise for any inconvenience that this may have caused. If there are any further issues please contact support@locomote.com

We are continuing to monitor for any further issues.

All users should now be able to log into the Locomote platform. We will continue to monitor and advise a resolution soon.

We are currently investigating reports that some users are unable to log into the Locomote platform. Our Engineering teams are currently investigating the issue.

We have successfully located and rectified the issue around users being unable to log into the Locomote platform. We apologise for any inconvenience that this may have caused. If there are any further issues please contact support@locomote.com

We are monitoring reports received that some users are unable to log into the Locomote platform. We are currently investigating the problem and will update the issue as soon as they come to hand.

The messaging functionality is now working as expected on all browsers. We apologise for any inconvenience this has caused. If there are any further issues please contact support@locomote.com

We are currently experiencing an issue in which messages within a trip are failing to send in browsers other than Chrome/Firefox eg. Microsoft Internet Explorer, Edge & Safari. Users of Chrome/Firefox can proceed with sending the message by refreshing the page after completion. We will have this resolved as soon as possible. We apologise for any inconvenience this may have caused during this time.

All users are now able to log into the Locomote Platform. We apologise for any inconvenience this has caused. If there are any further issues please contact support@locomote.com

All users should now be able to log into the Locomote platform. We will continue to monitor and advise a resolution soon.

We are currently investigating reports that some users are unable to log into the Locomote platform. We will continue to monitor and resolve any instances as quickly as possible

Resolved: All systems are now operational and trips can be created successfully. Please contact Travelport Locomote Support for any further issues.

Update: We are still experiencing issues creating trips. We'll continue to advise updates as we get more information.

We are currently experiencing issues where users are unable to create trips. It has been identified as a third party issue and is being treated as an urgent issue. A fix will be released soon.

Profiles are now able to be updated successfully. If you see any further issue please report them to Support as required. Thank you for your patience during this time.

Users are currently unable to update profiles. We are investigating the issue and will provide an update as soon as possible. We apologise for the inconvenience that this has caused.

The issue has now been resolved by the vendor Hertz. This has been tested on the platform and is working as expected.

We are monitoring reports received from car vendor Hertz that they are currently experiencing issues supplying rates into booking platforms. Hertz have escalated the issue internally and we will continue to update as advised.

This issue has now been resolved; all flights can now be searched and booked successfully. We apologise for any inconvenience that this may have caused

We have identified the cause of the "something went wrong" message travellers are seeing when attempting to use the Locomote booking tool. and are working to resolve this as quickly as possible. We apologise for any inconvenience caused.

We are investigating reports that travellers are unable to use the Locomote booking tool, receiving a "something went wrong" message. We are working to resolve this as quickly as possible.

All testing, logs and reports from clients indicate that this issue has now been resolved. If you have any further issues with updating your profile or require any support please contact us at support@locomote.com. Again we apologise for any inconvenience this may have caused.

We have investigated the current issue and believe that it has been rectified. If you do find an error, please update your profile and attempt to progress with your booking. If there are any outstanding errors please contact support@locomote. We apologise for any inconvenience caused.

We are currently investigating reports that travellers are unable to use the booking tool after attempting to update their profile. Please do not attempt to update any profiles until further notice We will provide updates as we learn more

All testing, logs and reports from clients indicate this has now been resolved. If you run into anything out of the ordinary, please contact our support team at support@locomote.com. We apologise for any inconvenience this may have caused.

Most travellers are now able to use the Locomote booking module again. We expect the situation to continue to improve over the next half hour or so.

We have identified the cause of the "something went wrong" message travellers are seeing when attempting to use the Locomote booking module. We are working to resolve this as quickly as possible.

We are investigating reports that travellers are unable to load the Locomote booking module. We will provide updates as we learn more.

This has been resolved; all flights can now be booked successfully. We apologise for any inconvenience that may have been caused.

We have identified the cause of this issue and are working on a fix.

When booking flights, users are seeing an error page "Something went wrong". We are working on a resolution and will update the issue when more details come to hand.

Our data provider has resolved this issue and service has been returned to normal. If you are still experiencing issues please contact support@locomote.com. We apologise for any inconvenience this caused.

Our data provider is continuing to work to resolve this issue. We will provide an update when the issue has been resolved.

Our data provider has identified an issue that is causing flight/hotel/car searches to return no (or slow) results, and is actively working to resolve the issue.

We are aware that some flight/hotel/car searches are currently returning no results. We are investigating and will provide updates as we learn more.

This has been resolved. If you are still experiencing issues please contact support@locomote.com. We apologise for any inconvenience this caused.

We are continuing to investigate as our highest priority.

We are aware of an issue currently affecting the Travel Management Platform which may be causing slow response times and/or errors. We are investigating as our highest priority.

This has been resolved; the booking app is now loading. If you are still experiencing issues please contact support@locomote.com. We apologise for any inconvenience this caused.

We are aware of an issue that is preventing the booking app from loading. We are investigating as our highest priority.

This has been resolved; Authorisers are now able to check out regardless of which other roles they have. We apologise for any inconvenience that this may have caused.

We apologise for any inconvenience this may be causing. A fix is currently in development; it is on track to be released tomorrow.

We are aware that when attempting to check out, some travellers are seeing the message "Trip contains no valid travellers." This happens to people who have the Authoriser role but do not have either the Travel Arranger or Company Administrator role. We are working on a fix as our highest priority.

The Locomote Booking App is now loading for all companies. If you are still experiencing issues, please let us know via support@locomote.com. We apologise for any inconvenience this may have caused.

We are aware of an issue that is preventing the Locomote Booking App from loading for some companies. We have identified the cause and are all hands on deck working on a fix.

We have successfully exported the remaining profiles, and the feedback we are receiving indicates that all the issues from earlier today have been resolved. If you are still experiencing difficulties, please contact us at support@locomote.com. Please accept our apologies for any inconvenience caused.

The majority of the issues from earlier today appear to now be resolved. We will continue to monitor this closely. There are a handful of profiles that are yet to be exported, which we are investigating.

We have identified the root cause for most, or possibly all of the current issues. We are reprocessing queues of emails, profile exports and other background jobs now, so most issues should be resolved in the next 15 minutes or so. We are investigating which, if any, of this morning's reported issues have not been resolved.

We are aware of an issue that is causing some emails not to be sent, some profiles not to be exported and some trips to appear incorrectly (or not at all) on the TMC dashboard. We are working to get a fix out as quickly as possible.

All users are now able to open trips as expected. Contact us via support@locomote.com and let us know if you see anything to the contrary. Please accept our sincere apologies for any inconvenience this may have caused.

We have identified the cause of this behaviour. An update to address it is under development and will be released as soon as possible.

Some users are seeing a "something went wrong" error when trying to open trips. We are investigating and will provide an update soon.

This is now resolved; we will continue to monitor. If you experience any issues, please contact support@locomote.com

All users are currently unable to sign in to Locomote. We are investigating and will provide an update shortly.

All searches are now returning results as expected. If you are still experiencing issues, please contact support@locomote.com. Thanks for your patience and apologies for any inconvenience caused.

Most flight searches are now returning results. We expect that any searches still not returning results will start doing so shortly.

We are aware of an issue that is preventing flight search results from appearing and are working to resolve this as quickly as possible.

This has been resolved; the warning message is now only displayed when it should be. We apologise for any confusion that may have been caused.

When creating a new trip, some users are seeing a warning that tells them that an Administrator needs to assign a Travel Management Consultant. This warning is being displayed in error and for the moment it can be safely ignored. Despite the warning, trips can be created and completed without error. A fix will be released soon.

No further issues have been observed or reported in the last several hours so this incident has been resolved. We apologise for the inconvenience.

Functionality has now been restored. We will continue to monitor and apologise for the inconvenience.

Some functionality relating to the Messages feature is degraded. We are working on restoring this functionality and apologise for the inconvenience.

This issue has been resolved for the majority of our clients. We expect the issue to be fully resolved for everyone soon. We apologise for the inconvenience.

We are aware of an outage that is causing the Travel Management Platform to display a "500" error. We are aware of the cause and expect the issue to be resolved soon.

No further issues have been seen since the root cause of this issue was resolved. We apologise again for any inconvenience.

Functionality has been restored. We will continue to monitor. Apologies for any inconvenience.

We are aware of a major outage that is preventing the Corporate Booking Tool from loading. We are investigating.

This issue is resolved. There have been no occurrences of this issue since the fix was released.

The external party involved in this incident has released a fix for this issue. We will continue to monitor.

Our workaround is continuing to work well. A permanent fix from the external party involved in this incident is under development; we will advise when it is in place.

We are continuing to monitor this issue. The workaround deployed on Friday is continuing to work well.

We are continuing to monitor this issue. The workaround deployed this morning is continuing to work well.

Locomote has deployed a workaround for this issue, and early testing is positive. We will continue to monitor, and work towards a permanent fix.

We are continuing to work with the external party on a fix. We are also investigating the possibility of implementing our own workaround, in case that can be completed quicker.

The booking tool is not loading for some users. Often it will load on subsequent attempts. We have identified that the source of this issue is an external party and are working with them to resolve this issue urgently.

An application server became unresponsive, preventing our Single Sign-On clients from signing in. The service was restarted and full service has now been restored.

This issue has been resolved, we will continue to monitor this closely.

Some users are currently unable to access the TMP. We are investigating the cause of this issue.

The issue with Profile Exporting to CBT (Corporate Booking Tool) has been resolved, any pending profile exports will be processed normally

We are currently experiencing issues exporting profiles to the CBT (Corporate Booking Tool). No data has been lost and the system should be back up shortly.