Skip to main content
If you’ve verified your wallet balances and noticed a discrepancy between Breezing and the block explorer (e.g., Etherscan), it usually means an API skipped a beat or missed a transaction during the sync. This guide covers how to fix the issue depending on whether or not you’ve already started working on the workspace.

​
Method 1: The “Fresh Start” Approach

Best for: Workspaces where you have not started categorizing or labeling transactions yet. The simplest and fastest way to fix a corrupted API pull is to delete the wallet and read it again.
  1. Navigate to the Wallets page.
  2. Select the problematic wallet.
  3. Click Settings and select Delete. This will completely remove the wallet and all its historical transactions from Breezing.
  4. Click the + (New) button, select Blockchain, paste the wallet address back in, name it, and re-pull the data via Network.
A fresh read will almost always resolve temporary API delays or skipped transactions.

​
Method 2: Re-pulling a Specific Date Range

Best for: Workspaces where you have started categorizing transactions in previous periods, but a newer period is missing data. If you’ve spent hours categorizing transactions from 2023, you do not want to delete the entire wallet and lose that work just because 2024 is missing a few transactions! Instead, you can delete and re-pull only the corrupted period.
  1. Go to your Dashboard.
  2. Identify the specific time period that is missing transactions (e.g., “I know everything up to 2023 is perfectly categorized, but early 2024 is corrupted”).
  3. Use the Filter or manually select the transactions from the problematic period (e.g., all 2024 transactions).
  4. Click Manage and select Delete to remove only those selected transactions. Your past work (e.g., 2023) remains safely in Breezing.
  5. Now, go back to the Wallets page and select that wallet.
  6. Click Get Latest Transactions.
  7. Adjust the date range to match the period you just deleted (e.g., Jan 1, 2024 to Present) and click Continue.
Breezing will re-pull only the missing period, ensuring you get the skipped transactions without overwriting your past accounting work.

​
Method 3: Adding Transactions Manually

Best for: Edge cases where a specific transaction simply will not sync via the API, or you’re missing a single internal transfer. If re-pulling the data still leaves you missing a specific transaction, you can manually insert it to balance the books.
  1. On the Dashboard, click the button to Add Transaction Manually.
  2. Enter the exact Transaction Hash, Timestamp, Token amount, Asset name, and Direction.
  3. Save the transaction. This manual entry will fill the gap and force the wallet balance to match the block explorer.
All right, cool. So, let’s say now you want to fix the balances on a specific wallet. Um, the best way to do that is if you haven’t started working on the wallets themselves, uh, the best way to do is to really just delete um, the actual entire wallet itself and then read it. Um, sometimes the API kind of skips a beat. So, I’m going to ahead and copy that here. Setting, delete, delete the wallet. And then I’m going to read the ops wallet again. Blockchain. Add the wallet in here. call ops wallet. Okay. Continue via network. And then just go ahead and hit it right there. And there it is. Off wallets re-dited. And then I can again verify these balances. But let’s say there’s a scenario where you already started working on the wallet itself and you now basically just want to like you know not delete the entire wallet because you’ve already started working on it but you know you’re missing some transactions let’s say. So let’s say you were already like labeling these transactions as like you know the ones in the past down here like as like other revenue or whatever it might be and you know there’s a specific like time period that you lost some transactions in u. And so what you do is you just delete that time period. So, let’s say May 29th and May 29th and Feb 18th and Feb 6. Let’s say I know everything from here. Let’s say let’s say everything in 2024 I’m just going to delete because I know the balances up to 2023 were good, but 2024 I knew something was fishy up was something fishy was going on there. So, I would hit manage. I would delete them. So, they’re gone. I only have up to 2023 transactions. I would then go back up here. I would get latest transactions again and I would see, okay, it’s pulling 2023 2025 again. Hit continue. So I’m letting it pull those extra 2024 transactions that I just deleted and anything kind of else that was missing during that period. So that’s predominantly because I had worked on the transactions in prior periods and I don’t want to get rid of that. So there it is pulled me the additional transactions here. I can see 2024 is repulled and I can then just check okay did they did it capture those transactions I had missed previously. Now if there’s a transaction that is not working even with this method. The other method is to just add these transactions in manually. So you can add them like this. Throw the hash in, throw all the details in and then add it manually. That also helps fill in the gaps on kind of like figuring out making sure the balances match. So that’s the way you reconcile the wallets, making sure the balances match.