Locus had 11 outages in the last 2 years — averaging 0.5 incidents per month.
There were 11 Locus outages since November 27, 2024. Each is summarised below — incident details, duration, and resolution information.
On 2024-11-14T12:26:59.264+0530, the Help & Support ticket creation from the dashboard failed due to an outdated Freshdesk API key in the secrets manager, affecting NV and IN stacks. Resolution was achieved by updating the API key.
On 2024-12-16T15:44:51.984+0530, the auto-assign error and unmasking of contact details impacted the TrackIQ component in the NV stack due to missing obfuscation logic in task-related APIs, leading to a compliance breach. The issue was resolved by 2024-12-17T14:34:18.303+0530 after implementing the necessary logic to maintain data obfuscation.
On 2024-12-19T14:02:37.220+0530, TDMS experienced an issue where tracking tour IDs were set to null, impacting dispatch assignments due to a bad commit. This issue was resolved by 2024-12-24T10:10:15.808+0530.
On 11/Nov/24 at 1:13 PM IST, the OrderIQ component on the IN stack experienced an issue where orders were incorrectly moving to PARK status after a tour was discarded. This was due to a faulty process that caused tours not to generate automatically, impacting operations. The issue was mitigated by a temporary update to the TDMS API.
On 2024-12-12T20:42:58.164+0530, Tour Dispatch Management System (TDMS) was impacted on the IN stack due to a bug in vehicle pro-assign plans dispatch, where empty tours were being dispatched erroneously. The issue was resolved by correcting the handling of the type field to avoid dispatching empty tours.
On 2025-01-14T20:40:51.865+0530, order creation was impacted in SolutionIQ on the IN stack due to files exceeding the row limit of 11,000, causing orders not to be processed. The issue was resolved by processing failed orders in batches and adding alerts for future occurrences.
On 19/Dec/24, there was an issue affecting TDMS on the IN stack where callbacks for shipments were not sent due to incorrect tour ID formats. The problem has been resolved by rolling back the problematic change and coordinating manual interventions for affected shipments.
On 2024-11-27T12:31:42.503+0530, a 5XX error occurred during invoice posting due to internal API endpoints being used instead of public ones on the IN stack. This issue prevented clients from accessing necessary APIs. The root cause was related to API endpoints being restricted to internal use. The issue has been resolved and service is restored.
On 2024-11-11T13:01:15.404+0530, the TDMS component in the IN stack allowed dispatch of tours with zero orders. This was due to a case where a tour was created from DIQ. The issue was identified and resolved with the latest release. The component is fully operational post-resolution.
On 2024-11-22T18:54:12.618+0530, Tour Dispatch Management System (TDMS) on the IN stack experienced an issue with rate-limiting internal API calls, causing a 'Too many requests' error. Rate limits were adjusted to a higher threshold, mitigating client-facing impacts and restoring full operations.
On November 27, 2024, there was an issue with the Tecor and Xpedigo carrier integrations where switching to an older implementation to reduce alerts caused new tracking information from them to be ignored silently, impacting order status updates. The incident was resolved by manually updating order statuses and ensuring that SMS notifications were appropriately managed.