Replies: 5 comments 1 reply
-
|
Hi there! This is an automated reply. Thank you for including debug information. You triggered an automated reply, because it looks like you're not running Firefly III version v6.5.4 or version v2.2.0 of the data importer. Please make sure to upgrade to the latest version of Firefly III (or the data importer) first. This may already solve your issue. If you are running the latest version, and this message is wrong, my apologies for the intrusion. |
Beta Was this translation helpful? Give feedback.
-
|
Note that I first spotted this issue quite some time ago so I cannot tell which Firefly version first introduced the bug. It may have been there ever since running totals were first implemented. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Hey, thanks for opening an issue. I'm aware of the issue, I'm opening and closing tickets as I find the cause of particular causes. If you have something I can replicate, I would be much obliged. Cheers, |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Support guidelines
I've found a bug and checked that ...
Description
I have a fairly long history of transactions on a bunch of accounts and at this point almost all running balances are wrong and cannot be relied on. That being said, chart on top of account view always shows correct values.
When looking at transaction history, it's not always clear when it "breaks" but apparently some transactions seem to contribute wildly incorrectly to running balances.
Here is one instance where I spotted the inconsistency "being born":
Note that transfer seems to "reset" the running total - i.e., instead of adding to the running total it just sets it to the transfer amount.
Debug information
Debug information generated at 2026-03-06 17:14:56 for Firefly III version v6.5.3.
**en_GB.UTF-8: ✅
Steps to reproduce
Unfportunately, I wasn't able to reproduce this issue in a controlled and reproducible manner.
Additional info
No response
Beta Was this translation helpful? Give feedback.
All reactions