All Docs
ChangelogMaking Tax DigitalUpdated March 6, 2026

v1.0.314 — Pipeline Auto-Fix: Unclassified Testing Agent Error

v1.0.314 — Pipeline Auto-Fix: Unclassified Testing Agent Error

Released: 2025-07-14
Type: Automated pipeline recovery release
Audience: Internal engineering

What Happened

Release v1.0.314 was automatically generated by the CI/CD pipeline after the testing agent encountered an unclassified error during a workflow run.

The error occurred when the pipeline attempted to dispatch a GitHub Actions workflow targeting the branch feat/rename-organisation-to-portfolio. The GitHub API responded that no ref could be found for that branch name:

No ref found for: feat/rename-organisation-to-portfolio
  https://docs.github.com/rest/actions/workflows#create-a-workflow-dispatch-event

Because the error did not match any known category, the pipeline classified it as unknown and escalated via an auto-fix release.

Impact

This release contains no user-facing changes. There is no impact to:

  • HMRC submission workflows
  • Bank feed imports or transaction categorisation
  • OAuth authentication or credential storage
  • Quarterly/annual filing processes
  • Any landlord or self-employed taxpayer data

Root Cause (Preliminary)

The most likely cause is that the branch feat/rename-organisation-to-portfolio was not present in the remote repository at the time the workflow dispatch was triggered. Possible reasons include:

  • The branch was deleted after a merge
  • The branch was renamed before being pushed
  • The branch was never pushed to the remote

Next Steps

  1. Investigate pipeline run 27c69eb7-8599-4cef-8324-7ce5351446d7 and agent job 89ccb195-d54e-428d-b122-1e6350744d9e for full context.
  2. Confirm the status of the feat/rename-organisation-to-portfolio branch — determine whether the rename-organisation-to-portfolio work is complete, in progress, or abandoned.
  3. Re-trigger the relevant workflow against the correct branch or ref if the work is still ongoing.
  4. Update error classification rules in the testing agent if this failure pattern is expected to recur.

This post was automatically generated from pipeline failure metadata. No manual code changes were included in this release.