[Bug]: GoCardless syncing way more data then used to (730 days back) #1133

Closed
opened 2026-02-28 19:33:20 -06:00 by GiteaMirror · 13 comments
Owner

Originally created by @leikoilja on GitHub (Jun 5, 2024).

Verified issue does not already exist?

  • I have searched and found no existing issue
  • I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

I have had a bank sync (Nordigen/GoCardless) enabled since 2023 - generally all good.
After the last upgrade to 24.6.0, UI has showed me that error happened and to resolve it - I would need to re-connect the sync (i believe it's a normal regular procedure for every Actual docker image update i do).
Normally, i remember Oauth onboarding modal showing that transactions for the past 90 days will be pulled such as this example image:
image

However, this time around when i connect bank integration i see that data seems to be pulled for the past 730 days 🤔
image

If i agree and go on - integration pulls tons of random data and all my previously linked accounts go bananas with ~160 new uncategorised transactions and probably many more auto-categorised, which i suppose comes from waaay back in time

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Mac OSX

Originally created by @leikoilja on GitHub (Jun 5, 2024). ### Verified issue does not already exist? - [X] I have searched and found no existing issue - [X] I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file) ### What happened? I have had a bank sync (Nordigen/GoCardless) enabled since 2023 - generally all good. After the last upgrade to 24.6.0, UI has showed me that error happened and to resolve it - I would need to re-connect the sync (i believe it's a normal regular procedure for every Actual docker image update i do). Normally, i remember Oauth onboarding modal showing that transactions for the past 90 days will be pulled such as this example image: <img width="409" alt="image" src="https://github.com/actualbudget/actual/assets/10655107/8d6392a5-0124-49b8-a342-aa936878c461"> However, this time around when i connect bank integration i see that data seems to be pulled for the past 730 days 🤔 <img width="769" alt="image" src="https://github.com/actualbudget/actual/assets/10655107/f30cc830-87f6-49a8-9c4a-e5cd50eee385"> If i agree and go on - integration pulls tons of random data and all my previously linked accounts go bananas with ~160 new uncategorised transactions and probably many more auto-categorised, which i suppose comes from waaay back in time ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Mac OSX
GiteaMirror added the bug label 2026-02-28 19:33:20 -06:00
Author
Owner

@tmoitie commented on GitHub (Jun 5, 2024):

👍 Also seems to be no longer respecting account start date, fetching transactions from long before I started using actual.

@tmoitie commented on GitHub (Jun 5, 2024): 👍 Also seems to be no longer respecting account start date, fetching transactions from long before I started using actual.
Author
Owner

@Brawl345 commented on GitHub (Jun 5, 2024):

I have the same problem with ING even though I set the "Starting Balance" to 1st February (when I started using ActualBudget) which prevented syncing older entries. This seems to no longer work.

EDIT: Workaround: Create a "pre" rule that zeroes out the amount and set a new category like "invalid transactions" or something and apply that to all before a certain date.

@Brawl345 commented on GitHub (Jun 5, 2024): I have the same problem with ING even though I set the "Starting Balance" to 1st February (when I started using ActualBudget) which prevented syncing older entries. This seems to no longer work. EDIT: Workaround: Create a "pre" rule that zeroes out the amount and set a new category like "invalid transactions" or something and apply that to all before a certain date.
Author
Owner

@leikoilja commented on GitHub (Jun 5, 2024):

I have the same problem with ING even though I set the "Starting Balance" to 1st February (when I started using ActualBudget) which prevented syncing older entries. This seems to no longer work.

EDIT: Workaround: Create a "pre" rule that zeroes out the amount and set a new category like "invalid transactions" or something and apply that to all before a certain date.

hm, thanks for sharing your workaround.
i use actual for historical records and would love to avoid extra unnecessary records messing up things. Have disabled GoCardless sync for now... back to manual entries until the issue is fixed haha 😅

@leikoilja commented on GitHub (Jun 5, 2024): > I have the same problem with ING even though I set the "Starting Balance" to 1st February (when I started using ActualBudget) which prevented syncing older entries. This seems to no longer work. > > EDIT: Workaround: Create a "pre" rule that zeroes out the amount and set a new category like "invalid transactions" or something and apply that to all before a certain date. hm, thanks for sharing your workaround. i use actual for historical records and would love to avoid extra unnecessary records messing up things. Have disabled GoCardless sync for now... back to manual entries until the issue is fixed haha 😅
Author
Owner

@MatissJanis commented on GitHub (Jun 5, 2024):

Folks on Discord have also reported this issue. The current group-think there is that this has to be related with the recent incident/maintenance Nordigen performed.

Apparently folks are able to reproduce the same issue on older versions of Actual (can someone verify?). That would cancel out Actual as the culprit.

@MatissJanis commented on GitHub (Jun 5, 2024): Folks on Discord have also reported this issue. The current group-think there is that this has to be related with the recent incident/maintenance Nordigen performed. Apparently folks are able to reproduce the same issue on older versions of Actual (can someone verify?). That would cancel out Actual as the culprit.
Author
Owner

@RonaldVleeming commented on GitHub (Jun 5, 2024):

Apparently folks are able to reproduce the same issue on older versions of Actual (can someone verify?). That would cancel out Actual as the culprit.

I have the same issue on v24.5.0, so it's definitely a change on the side of GoCardless/Nordigen.

For me it imports all transactions since I've opened the account at KNAB (>2 years ago)

@RonaldVleeming commented on GitHub (Jun 5, 2024): > Apparently folks are able to reproduce the same issue on older versions of Actual (can someone verify?). That would cancel out Actual as the culprit. I have the same issue on v24.5.0, so it's definitely a change on the side of GoCardless/Nordigen. For me it imports all transactions since I've opened the account at KNAB (>2 years ago)
Author
Owner

@leikoilja commented on GitHub (Jun 5, 2024):

Folks on Discord have also reported this issue. The current group-think there is that this has to be related with the recent incident/maintenance Nordigen performed.

Apparently folks are able to reproduce the same issue on older versions of Actual (can someone verify?). That would cancel out Actual as the culprit.

can also verify the same issue on v24.5.0, since i did a roll-back after upgrade and tried there as well :)

@leikoilja commented on GitHub (Jun 5, 2024): > Folks on Discord have also reported this issue. The current group-think there is that this has to be related with the recent incident/maintenance Nordigen performed. > > Apparently folks are able to reproduce the same issue on older versions of Actual (can someone verify?). That would cancel out Actual as the culprit. can also verify the same issue on v24.5.0, since i did a roll-back after upgrade and tried there as well :)
Author
Owner

@johnnymerayo commented on GitHub (Jun 5, 2024):

Same problem here with Lloyds bank (UK)

@johnnymerayo commented on GitHub (Jun 5, 2024): Same problem here with Lloyds bank (UK)
Author
Owner

@npasslick commented on GitHub (Jun 5, 2024):

Same problem here :(
Biggest problem is that the starting date in Actual is not respected anymore, I now have over 1200 uncategorized transactions messing up everything

@npasslick commented on GitHub (Jun 5, 2024): Same problem here :( Biggest problem is that the starting date in Actual is not respected anymore, I now have over 1200 uncategorized transactions messing up everything
Author
Owner

@Kidglove57 commented on GitHub (Jun 5, 2024):

I’m syncing via Go Cardless with Starling (UK) and cards with Amex and Halifax. The only problem I have had so far is (a) having to unlink and relink GoCardless (b) a random incorrect import at Starling in July ‘23. Phew!

@Kidglove57 commented on GitHub (Jun 5, 2024): I’m syncing via Go Cardless with Starling (UK) and cards with Amex and Halifax. The only problem I have had so far is (a) having to unlink and relink GoCardless (b) a random incorrect import at Starling in July ‘23. Phew!
Author
Owner

@AlfHou commented on GitHub (Jun 6, 2024):

I just set up my actual server, and I'm experiencing the same issue. My bank accounts are either not able to sync, or when they are they stop working after a few days.

@AlfHou commented on GitHub (Jun 6, 2024): I just set up my actual server, and I'm experiencing the same issue. My bank accounts are either not able to sync, or when they are they stop working after a few days.
Author
Owner

@npasslick commented on GitHub (Jun 6, 2024):

Everyone, please try syncing again — the issue might be resolved on GoCardless' end

@npasslick commented on GitHub (Jun 6, 2024): Everyone, please try syncing again — the issue might be resolved on GoCardless' end
Author
Owner

@Brawl345 commented on GitHub (Jun 6, 2024):

Thanks for the reply, it seems to work now, no longer getting older transactions!

EDIT: Side note: If you have already synced old data and deleted it I recommend to reset sync in the settings because it bloated my database to >20 MB and made sync unusable on my phone. Export your data as a backup first!

@Brawl345 commented on GitHub (Jun 6, 2024): Thanks for the reply, it seems to work now, no longer getting older transactions! EDIT: Side note: If you have already synced old data and deleted it I recommend to reset sync in the settings because it bloated my database to >20 MB and made sync unusable on my phone. Export your data as a backup first!
Author
Owner

@leikoilja commented on GitHub (Jun 7, 2024):

have re-tried it again now and can confirm that the issues is resolved, hence closing this :)
if someone is still experiencing this issues after re-linking - we ll re-open

@leikoilja commented on GitHub (Jun 7, 2024): have re-tried it again now and can confirm that the issues is resolved, hence closing this :) if someone is still experiencing this issues after re-linking - we ll re-open
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#1133