Analysis/Intelligence: P1

Update timeline

1. resolved Jun 30, 2026, 04:11 PM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Jun 30, 2026, 04:18 PM UTC

   Multiple Go.gov customers are experiencing a functional disruption that impacts the availability of travel allowance data in Analysis/Intelligence reports. Users with permissions to access, run, and view reports in the Analysis/Intelligence service may notice that Travel Request Key values are missing from both standard and custom reports. Our investigation has confirmed that, instead of displaying the expected Travel Request Key values, affected reports are showing a value of “-1.” Workaround: A workaround for this issue is not available at this time. Since our last update the priority of this incident has been upgraded from P2 to P1. The Incident Response Team (IRT) has identified the root cause of this issue as an anomaly within the data mapping logic. The team is actively developing a corrective fix. Once development is complete, the fix will undergo testing in an internal environment to verify that it resolves the identified data mapping issue before it is deployed to production. Following the production deployment, the IRT will conduct additional validation and monitoring to confirm the effectiveness of the fix within affected customer environments and ensure normal functionality has been restored. We will post the next incident communication at 7:00PM UTC on 30 June 2026, or sooner should a significant change occur.

3. resolved Jun 30, 2026, 06:57 PM UTC

   Multiple Go.gov customers are experiencing a functional disruption that impacts the availability of travel allowance data in Analysis/Intelligence reports. Users with permissions to access, run, and view reports in the Analysis/Intelligence service may notice that Travel Request Key values are missing from both standard and custom reports. Our investigation has confirmed that, instead of displaying the expected Travel Request Key values, affected reports are showing a value of “-1.” Other expense data, unrelated to travel request keys for travel allowances, is available and unaffected by this issue. Workaround: A workaround for this issue is not available at this time. The Incident Response Team (IRT) has completed development of a fix and is currently validating it in an internal testing environment. At this stage, testing is focused on two objectives. First, confirming that the fix successfully resolves the identified data-mapping anomaly. Second, reproducing the Travel Request Key issue by using a copy of an affected report from the customer environment within the internal test environment, and evaluating the impact of the data correction on report output. We will provide additional details regarding production deployment plans and timelines once internal validation is complete and testing confirms the fix is performing as expected. We will post the next incident communication at 10:00PM UTC on 30 June 2026, or sooner should a significant change occur.

4. resolved Jun 30, 2026, 08:49 PM UTC

   Multiple Go.gov customers experienced a functional disruption that impacted the availability of travel allowance data in Analysis/Intelligence reports. Users with permissions to access, run, and view reports in the Analysis/Intelligence service may have noticed that Travel Request Key values were missing from both standard and custom reports. Our investigation has confirmed that, instead of displaying the expected Travel Request Key values, affected reports showed a value of “-1.” Other expense data, unrelated to travel request keys for travel allowances, was available and unaffected by this issue. The fix has been deployed to the production environment and validation testing has yielded positive results. 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.

5. resolved Jun 30, 2026, 09:25 PM UTC

   Multiple Go.gov customers experienced a functional disruption that impacted the availability of travel allowance data in Analysis/Intelligence reports. Users with permissions to access, run, and view reports in the Analysis/Intelligence service may have noticed that Travel Request Key values were missing from both standard and custom reports. Our investigation has confirmed that, instead of displaying the expected Travel Request Key values, affected reports showed a value of “-1.” Other expense data, unrelated to travel request keys for travel allowances, was available and unaffected by this issue. Workaround: A workaround for this issue is not available during service impact. The Incident Response Team identified a data-mapping issue as the root cause and implemented a corrective fix restoring the expected travel request data values in travel allowance reports. 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.

6. resolved Aug 04, 2026, 12:08 PM UTC

   Impact as Reported: Multiple Go.gov customers experienced a functional disruption that impacted the availability of travel allowance data in Analysis/Intelligence reports. Users with permissions to access, run, and view reports in the Analysis/Intelligence service may have noticed that Travel Request Key values were missing from both standard and custom reports. Our investigation has confirmed that, instead of displaying the expected Travel Request Key values, affected reports showed a value of “-1.” Other expense data, unrelated to travel request keys for travel allowances, was available and unaffected by this issue. Root Cause An issue in the Analytics archiving process caused certain Travel Allowance records to not be correctly linked to their associated Travel Requests in reporting. As a result, affected records were assigned a default Travel Request key value of -1, leading to incomplete and inaccurate reporting data for impacted entities. The issue was traced to a code change deployed in April 2026 as part of an effort to address other Travel Allowance matching scenarios. The update introduced a defect in the archive matching process, which evaluates Travel Allowance events after they are loaded into a staging table. Under specific conditions where multiple system-generated events were present, the matching logic incorrectly selected only the first event and excluded subsequent events required to establish the relationship between Travel Allowance and Travel Request records. This caused valid records to be omitted from the matching process and prevented the associated Travel Request key from being populated. Identification of the root cause was delayed because the issue initially appeared to be related to source data quality. Early customer reports contained incorrect key values and inconsistent examples, which led investigators to focus on potential upstream data issues. In addition, limited visibility into the Travel Allowance creation process, restricted access to customer data, and delays in obtaining subject matter expertise across teams extended the investigation timeline. Once a live demonstration of the business workflow was provided and the relevant event-generation behaviour was understood, the Analytics team was able to isolate the archive matching defect and develop a fix. The issue was resolved by correcting the archive matching logic, deploying the fix to production, and reprocessing the affected Travel Allowance data to restore the missing relationships and reporting values. Corrective Actions To prevent recurrence and improve the timeliness of future investigations, the following actions have been completed or identified: Corrected the archive matching logic to ensure all relevant Travel Allowance events are evaluated during processing and that valid Travel Request relationships are not excluded. Reprocessed affected Travel Allowance data by reloading the impacted archive records, restoring the correct Travel Request key values in reporting. Review and expand test coverage for Travel Allowance archiving and matching scenarios, including workflows involving multiple system-generated events, to detect similar defects before deployment. Improve validation and monitoring of archive-processing outcomes to identify unexpected increases in unmatched Travel Allowance records. Enhance operational documentation for Travel Allowance processing, event generation, and archive matching to support more efficient troubleshooting. Establish clearer cross-team escalation and engagement procedures to ensure issues requiring expertise from multiple organizations are investigated without unnecessary delays. Review access requirements and operational processes to reduce investigation delays caused by restricted visibility into customer data and environment-specific behaviours. Improve collaboration and knowledge-sharing between Analytics, Spend, Support, and Delivery teams to enable faster identification of dependency-related issues and more effective incident resolution.