The inactive accounts lightning bolt fix — OL-393-specific: In QB's Chart of Accounts → click View at the bottom → check "Include inactive" → look for any bank account marked inactive that still has a lightning bolt icon (indicating it's still connected to bank feeds). Right-click the account → Edit Account → Bank Feed Settings → Deactivate All Online Services → OK → Save & Close. Do this for every inactive account with a lightning bolt. These ghost bank feed connections silently interfere with active account downloads and produce OL-393. After deactivating all inactive connections, restart QB and retry.

Inactive Accounts with Active Bank Feed Connections

OL-393-specific cause — accounts that were closed or marked inactive in QB but still have bank feed connections (lightning bolt icon) create silent conflicts. When QB downloads transactions for active accounts, the inactive accounts' stale bank feed connections interfere. Deactivating all online services on inactive lightning-bolt accounts resolves this.

Bank Server Timeout or Maintenance

The bank's server is temporarily unavailable, in maintenance, or responding too slowly for QB to complete the download. QB establishes the connection (unlike OL-332 where auth fails) but the download is abandoned before completion. Waiting and retrying resolves this cause without any configuration changes.

Incorrect Account Setup in QB

The bank account linked in QB doesn't match the account at the bank (account number changed, account was replaced with a new account number, or the bank changed an account type). QB connects successfully but the bank returns data that doesn't match what QB expects, interrupting the download with OL-393.

Corrupted Company File Data

Data damage in the company file's bank feed section can cause OL-393 on every download attempt. The test company file diagnostic confirms this: if the same bank account downloads successfully in a fresh test company, the main company file has bank feed data corruption. File Doctor can repair minor cases.

Unacknowledged Bank Security Alerts

Banks sometimes interrupt in-progress downloads if there are unacknowledged security notifications in the account (multi-factor auth prompts, updated terms, security questions). QB receives a partial response and reports OL-393. Logging into the bank's website and clearing all notifications before retrying resolves this.

Unstable Internet Connection

OL-393 literally means "connection was not able to complete" — an unstable internet connection that drops mid-download is a straightforward cause. Unlike OL-332 (credential failure before connection) or OL-301 (account issue at the bank), OL-393 can simply be a network stability problem. A wired connection retry often resolves this.

METHOD 1 Check Bank Website + Deactivate Inactive Lightning-Bolt Accounts OL-393-specific — resolves most cases

METHOD 2 Test Company File + Deactivate/Reactivate Bank Feed Identify if it's company file or bank server issue

METHOD 3 Check TLS Settings + Switch to Classic Mode Security protocol or bank feed mode mismatch

METHOD 4 Run File Doctor + Update QB + Use Web Connect Manually Company file damage or persistent bank server issue

What is a lightning bolt icon on a bank account in QB?

In QuickBooks Desktop, a lightning bolt icon next to an account in the Chart of Accounts indicates that the account has an active bank feed connection — it's linked to online banking and QB will attempt to download transactions for it. When you mark an account as inactive (because you closed the bank account or stopped using it), the account disappears from the default Chart of Accounts view but often retains its bank feed connection. The lightning bolt persists on the inactive account, and QB silently tries to download from that closed/inactive account during every bank feed update. This failed connection attempt can disrupt the downloads for your active accounts, producing OL-393. The fix is to show inactive accounts (check "Include Inactive" at the bottom of Chart of Accounts), find the lightning-bolt inactive accounts, and deactivate their online services.

How is OL-393 different from OL-332?

Both are OL-series bank feed errors and both use the same test company file diagnostic — but they fail at different pipeline stages. OL-332 is an authentication failure: QB couldn't even start the download because the customer ID or PIN was rejected by the bank. The connection was refused before any data transfer began. OL-393 is a download interruption: QB successfully authenticated and the download began, but was cut off before completing. This is why OL-393 often says "was not able to bring all of your transaction information up to date" — some data may have transferred before the interruption. The inactive lightning-bolt accounts fix is specific to OL-393 because those stale connections interfere with ongoing downloads; they don't affect OL-332's pre-authentication stage.