Expense, Request: P1

Update timeline

1. resolved Jun 09, 2026, 06:03 PM UTC

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

2. resolved Jun 09, 2026, 06:31 PM UTC

   External Reporting has identified functional disruptions affecting GO.gov user expense report and travel request submissions. Users are able to submit expense reports and travel requests without receiving an errors; however, the backend workflow fails to complete, preventing reimbursement processing. As a result, submitted expense reports and travel requests remain stalled with no progression in the backend workflow. These submissions will not be processed or completed until the issue is resolved. Unfortunately, a workaround is not available for this issue. The Incident Response Team (IRT) is gathering and recent changes are currently under investigation as a potential root cause. Our next update will be in one hour or sooner should a significant change occur.

3. resolved Jun 09, 2026, 07:31 PM UTC

   External Reporting has identified functional degradations affecting GO.gov user expense report and travel request submissions. Users are able to submit expense reports and travel requests without receiving an errors; however, the backend workflow fails to complete, preventing reimbursement processing. As a result, submitted expense reports and travel requests remain stalled with no progression in the backend workflow. These submissions will not be processed or completed until the issue is resolved. Unfortunately, a workaround is not available for this issue. The Incident Response Team (IRT) performed a revert of a recent change that was deemed a potential root cause of the stalled reports and requests. The IRT is now performing investigation to confirm if both pending reports and new reports are processing as expected. Our next update will be in one hour or sooner should a significant change occur.

4. resolved Jun 09, 2026, 08:39 PM UTC

   External Reporting has identified functional degradations affecting GO.gov user expense report and travel request submissions. Users are able to submit expense reports and travel requests without receiving an errors; however, the backend workflow fails to complete, preventing reimbursement processing. As a result, submitted expense reports and travel requests remain stalled with no progression in the backend workflow. These submissions will not be processed or completed until the issue is resolved. Unfortunately, a workaround is not available for this issue. Following the revert, some recovery has been observed when processing newly created reports. However, additional monitoring and research is currently underway to ensure system performance is returned to normal levels. Our next update will be in one hour or sooner should a significant change occur.

5. resolved Jun 09, 2026, 09:41 PM UTC

   External Reporting has identified functional degradations affecting GO.gov user expense report and travel request submissions. Users are able to submit expense reports and travel requests without receiving an errors; however, the backend workflow fails to complete, preventing reimbursement processing. As a result, submitted expense reports and travel requests remain stalled with no progression in the backend workflow. These submissions will not be processed or completed until the issue is resolved. Unfortunately, a workaround is not available for this issue. Following a brief time of some recovery, the IRT is now observing continued impact. Investigation into root cause is ongoing. Our next update will be on hour or sooner should a significant change occur.

6. resolved Jun 09, 2026, 10:40 PM UTC

   External Reporting has identified functional degradations affecting GO.gov user expense report and travel request submissions. Users are able to submit expense reports and travel requests without receiving an errors; however, the backend workflow fails to complete, preventing reimbursement processing. As a result, submitted expense reports and travel requests remain stalled with no progression in the backend workflow. These submissions will not be processed or completed until the issue is resolved. Unfortunately, a workaround is not available at this time. The IRT has identified a potential service configuration issue and is working with the internal teams to deploy the required fix. Investigation continues to validate the fix and address the ongoing impact. We will post the next incident communication at or before 11:40 PM UTC on 09 June 2026.

7. resolved Jun 09, 2026, 11:46 PM UTC

   External Reporting has identified functional degradations affecting GO.gov user expense report and travel request submissions. Users are able to submit expense reports and travel requests without receiving any errors; however, the backend workflow fails to complete, preventing reimbursement processing. As a result, submitted expense reports and travel requests remain stalled with no progression in the backend workflow. These submissions will not be processed or completed until the issue is resolved. Unfortunately, a workaround is not available at this time. The Incident Response Team has narrowed down the issue to a potential timeout configuration issue and is working with the internal teams to apply the configuration fix and validate service recovery. Our next update will be in two hours or sooner should a significant change occur.

8. resolved Jun 10, 2026, 01:44 AM UTC

   External Reporting has identified functional degradations affecting GO.gov user expense report and travel request submissions. Users are able to submit expense reports and travel requests without receiving any errors; however, the backend workflow fails to complete, preventing reimbursement processing. As a result, submitted expense reports and travel requests remain stalled with no progression in the backend workflow. These submissions will not be processed or completed until the issue is resolved. The IRT has deployed the fix, and they are working with internal teams to validate impacted transactions and confirm successful recovery processing. Our next update will be in two hours or sooner should a significant change occur.

9. resolved Jun 10, 2026, 03:31 AM UTC

   External Reporting has identified functional degradations affecting the GO.gov user expense report and travel request submissions. Users are able to submit expense reports and travel requests without receiving any errors; however, the backend workflow fails to complete, preventing reimbursement processing. As a result, submitted expense reports and travel requests remain stalled with no progression in the backend workflow. These submissions will not be processed or completed until the issue is resolved. Unfortunately, a workaround is not available at this time. The Incident Response Team is coordinating with the external provider and will hold a working session to review recovery options for impacted expense reports and requests, including safe reprocessing of failed transactions and handling of partially processed items. The incident will remain open until recovery options are validated and agreed upon, and successful processing of impacted transactions is confirmed prior to full incident resolution. We will post the next incident communication at or before 12:00 AM UTC on 11 June 2026.

10. resolved Jun 10, 2026, 03:46 PM UTC

    User impact has changed since our last update. Go.gov users are now able to successfully submit new expense reports and travel requests. However, external reporting indicates that approximately 40 previously impacted report and request submissions did not complete the backend workflow during the active incident and remain stalled at this time. Impacted users were not notified of the failure at the time of submission. Unfortunately, a workaround to manually trigger previously impacted reports is not available at this time. The Incident Response Team (IRT) has confirmed that new report and request submissions are now processing successfully. Efforts are currently underway to trigger completion of the backend workflows for submissions that stalled during the period of impact. We will post the next incident communication at or before 12:00AM UTC on 11 June 2026.

11. resolved Jun 10, 2026, 10:14 PM UTC

    External Reporting identified functional degradations affecting GO.gov user expense report and travel request submissions. Users were able to submit expense reports and travel requests without receiving any errors; however, the backend workflow failed to complete, preventing reimbursement processing. As a result, submitted expense reports and travel requests remained stalled with no progression in the backend workflow. These submissions could not be processed or completed until the issue was resolved. The Incident Response Team (IRT) took action to correct the back end workflow for new request and expense report submissions. Secondary actions were taken to address request and expense report submissions that were impacted during the time of impact. Unfortunately, a workaround to manually trigger previously impacted reports was not available during the time of impact. Services have returned to normal operating levels. We will activate an extended monitoring performance for the next 24 hours to verify stability. Once verified as stable the incident will be resolved.

12. resolved Jun 11, 2026, 09:42 PM UTC

    External Reporting identified functional degradations affecting GO.gov user expense report and travel request submissions. Users were able to submit expense reports and travel requests without receiving any errors; however, the backend workflow failed to complete, preventing reimbursement processing. As a result, submitted expense reports and travel requests remained stalled with no progression in the backend workflow. These submissions could not be processed or completed until the issue was resolved. There was no available workaround during the time of impact. The Incident Response Team took action to extend allowed submission processing times. Additionally, safeguards were added to prompt automatic retries should a temporary issue occur. 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.

13. resolved Jul 10, 2026, 05:10 PM UTC

    External Reporting identified functional degradations affecting GO.gov user expense report and travel request submissions. Users were able to submit expense reports and travel requests without receiving any errors; however, the backend workflow failed to complete, preventing reimbursement processing. As a result, submitted expense reports and travel requests remained stalled with no progression in the backend workflow. These submissions could not be processed or completed until the issue was resolved. The incident occurred following an update to an underlying JSON processing library to support and maintain the platform. This library modified the default ordering of data fields to be alphabetical by default. While this change was fully aligned with industry standards, which do not guarantee any specific field order, the client's systems were not able to process the updated JSON output. This caused expense report and travel request approvals to remain in a ‘Pending Validation’ status after the client's systems acknowledged receiving the output. Corrective Actions: The Incident Response Team temporarily reverted the update to give the client time to modify their systems to not depend on field order when processing JSON outputs. Once reverted, new expense reports and travel requests were confirmed working. However, existing reports remained in 'Pending Validation" state because their system was unable to retry the request after they had acknowledged receiving it. The Incident Response Team proceeded to work with the client to force the system to reprocess the affected requests. During the reprocessing, a known issue with some requests timing out delayed the ability to reprocess the requests. The Incident Response Team expedited an update to resolve the timeout issue to prevent further delays in reprocessing the requests. Working closely with support and the client, the Incident Response Team was able to complete the reprocessing of the existing reports and resolve the issue. The following actions are recommended for the client to to improve the integration with SAP Concur: Update the integration to process JSON outputs to follow RFC 8259 standard to not depend on field ordering Update the acknowledgment of receiving JSON output after successfully parsing the output. This enables SAP Concur to automatically retry sending outputs if there are issues with existing reports remaining in 'Pending Validation' state.