Split Issue: Wrong Transaction is used

[Fontiveros]

This seems to be a recurring issue with using Tiller with Google Sheets and the splitting feature.

Try to split a transaction and the wrong transaction is used. Most of the time, splitting works, but other times like all this weekend, the neighboring transaction is used. Here is an example, the highlighted $9.84 is the transaction, I’m wanting to split, but it pulls in the neighboring -$21.44.

I use Safari on Mac as my main browser. Whenever Splitting acts up, I tend to switch to Chrome and Split works in Chrome.

Not today. Splitting in Chrome today pulls in a completely random transaction, see reply for Chrome experience since I can only upload one image:

Same $9.84 transaction I’m trying to split in Chrome, but it pulls in the $30.02 which is came in a month later.

This happens if I use Split via Sheet’s menu or via the sidebar.

I’ve removed all filters thinking it could be related. SO this is UNfiltered view of Transactions.

Using a MacBook Air M4 on Safari (v26) and Chrome (140.0.7339.134) on MacOS 26.

Thank you.

Fontiveros

[Fontiveros]

Here is the same Transaction in Chrome pulling a transaction from a recent transaction

[Mark.S]

Interesting, what happens if you re-select the transaction you want, while Split Transaction is active, and then select the refresh in the Split Transaction sidebar? Maybe select a couple different transactions to see what changes.

[Fontiveros]

Super annoying. After I went in and manually split 25 transactions… the Tiller Split function now works.

This is a recurring issue for me, so I will post back next it happens. BUT I will use the refresh function next time and report back.

[heather]

Thanks for reporting this @Fontiveros - we’ll log it as a bug to investigate and see if we can reproduce.

For greater context, our product team prioritizes bugs, issues, and requests based on the severity of the issue and how many customers are impacted or requesting this feature. To provide insight on expectations, issues like this may not be actioned for many months or at all if it’s not a widespread issue. That timeline is based on the team’s current existing log of issues and upcoming feature releases which is subject to change.