Skip to main content
All Docs
FeaturesMaking Tax DigitalUpdated April 1, 2026

Bug Fix: TrueLayer Bank Connection Showing "Connection Failed" Despite Successful Link

Bug Fix: TrueLayer Bank Connection Showing "Connection Failed" Despite Successful Link

Version: 1.0.479 · Date: 2025-07-14 · Type: Bug Fix


What Was the Problem?

Users connecting their bank accounts via open banking (TrueLayer) were seeing a "connection failed" banner at the top of the app immediately after completing the connection flow — even though the connection to TrueLayer had been successfully established.

The symptoms were:

  • The open banking authorisation with TrueLayer completed without error.
  • The app displayed a "connection failed" status message.
  • The last sync timestamp updated correctly to "today", suggesting the platform had communicated with TrueLayer.
  • Despite this, no transactions were imported into the app.

This was confirmed with a Barclays account connected via open banking, but could affect any bank supported through the TrueLayer integration.


What Was the Root Cause?

The app was incorrectly interpreting the post-connection state returned by TrueLayer. Although the OAuth handshake completed successfully and a sync was triggered, the internal status handler was not correctly mapping TrueLayer's success response to a connected state — causing the UI to show a failure and the transaction import pipeline to abort.


What Has Been Fixed?

The connection status handling for TrueLayer has been corrected. After completing the open banking authorisation:

  • The app now correctly reflects a successful connection in the account status UI.
  • The "connection failed" banner no longer appears for successfully connected accounts.
  • Transactions are imported as expected following a successful sync.

Who Is Affected?

This fix affects any user who:

  • Connected (or attempted to connect) a bank account via TrueLayer open banking.
  • Saw a "connection failed" message after completing the bank authorisation flow.
  • Found that transactions were not appearing despite the last sync showing a recent timestamp.

If you experienced this issue, reconnecting your bank account after updating to v1.0.479 should resolve it and begin importing your transactions correctly.


Next Steps

If your bank account still shows a failed connection status after this update, try the following:

  1. Navigate to Settings → Bank Connections.
  2. Disconnect the affected account.
  3. Re-add the account using the open banking flow.
  4. Confirm that transactions appear in your transaction list after the sync completes.

If you continue to experience issues, please contact support with your account details and the name of your bank.