github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #5743] [Bug]: Sync failure (file too large) #9423

New Issue
Closed
opened 2026-04-10 19:41:53 -05:00 by GiteaMirror · 13 comments
GiteaMirror commented 2026-04-10 19:41:53 -05:00
Owner
Copy Link

Originally created by @kcollett on GitHub (Sep 19, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5743

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

The app asked me to open a github issue for a sync failure.

How can we reproduce the issue?

Not sure.

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Microsoft Edge

Operating System

Mac OSX

Originally created by @kcollett on GitHub (Sep 19, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5743 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? The app asked me to open a github issue for a sync failure. ### How can we reproduce the issue? Not sure. ### Where are you hosting Actual? Pikapods ### What browsers are you seeing the problem on? Microsoft Edge ### Operating System Mac OSX
GiteaMirror added the bug label 2026-04-10 19:41:53 -05:00
GiteaMirror commented 2026-04-10 19:41:54 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Sep 19, 2025):

Can you give more detail about what happened? What provider? When did it happen?

<!-- gh-comment-id:3312112835 --> @youngcw commented on GitHub (Sep 19, 2025): Can you give more detail about what happened? What provider? When did it happen?
GiteaMirror commented 2026-04-10 19:41:54 -05:00
Author
Owner
Copy Link

@kcollett commented on GitHub (Sep 19, 2025):

I didn't do anything; the app presented the message after a sync failure. I'm not sure what you mean by provider.

Edit: The popup that is displayed says somthing like "We had problems syncing your changes." After it appears, the Sync in the upper right corner changes color and says something like "Sync failure". (Neither of these indicators persist, so my I might have the exact wording wrong.)

<!-- gh-comment-id:3312169424 --> @kcollett commented on GitHub (Sep 19, 2025): I didn't do anything; the app presented the message after a sync failure. I'm not sure what you mean by provider. Edit: The popup that is displayed says somthing like "We had problems syncing your changes." After it appears, the Sync in the upper right corner changes color and says something like "Sync failure". (Neither of these indicators persist, so my I might have the exact wording wrong.)
GiteaMirror commented 2026-04-10 19:41:55 -05:00
Author
Owner
Copy Link

@kcollett commented on GitHub (Sep 19, 2025):

Looking at the documentation under 'What Does Resetting Sync" Mean?' (probably should fix those quotes) (at https://actualbudget.org/docs/getting-started/sync/#what-does-resetting-sync-mean) it says this towards:

Actual will always guide you through this. It tracks the status of all your files and will notify you if something is wrong and give you steps to fix the problem. If you want to manually reset sync, you can do that in settings.

I'm not seeing any evidence of this (unless opening a bug and following the responses to that bug is what it's referring to).

<!-- gh-comment-id:3312243222 --> @kcollett commented on GitHub (Sep 19, 2025): Looking at the documentation under 'What Does Resetting Sync" Mean?' (probably should fix those quotes) (at https://actualbudget.org/docs/getting-started/sync/#what-does-resetting-sync-mean) it says this towards: > Actual will always guide you through this. It tracks the status of all your files and will notify you if something is wrong and give you steps to fix the problem. If you want to manually reset sync, you can do that in settings. I'm not seeing any evidence of this (unless opening a bug and following the responses to that bug is what it's referring to).
GiteaMirror commented 2026-04-10 19:41:55 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Sep 19, 2025):

Oh, so a server sync issue, not a bank sync issue. Try viewing your budget in a private window. If that works and you can see your budget just fine and it doesn't have issues, then you can delete your browser data for the budget site and things probably will be fine

<!-- gh-comment-id:3312881946 --> @youngcw commented on GitHub (Sep 19, 2025): Oh, so a server sync issue, not a bank sync issue. Try viewing your budget in a private window. If that works and you can see your budget just fine and it doesn't have issues, then you can delete your browser data for the budget site and things probably will be fine
GiteaMirror commented 2026-04-10 19:41:55 -05:00
Author
Owner
Copy Link

@kcollett commented on GitHub (Sep 20, 2025):

I tried the private window, but it seems to be stuck at "Downloading...". (Looking at the PikaPods logs, it says "PayloadTooLargeError: request entity too large".)

I'm not sure what you mean by the "budget site". I have AB windows open on two different machines, both using the same PikaPods instance.

<!-- gh-comment-id:3314913107 --> @kcollett commented on GitHub (Sep 20, 2025): I tried the private window, but it seems to be stuck at "Downloading...". (Looking at the PikaPods logs, it says "PayloadTooLargeError: request entity too large".) I'm not sure what you mean by the "budget site". I have AB windows open on two different machines, both using the same PikaPods instance.
GiteaMirror commented 2026-04-10 19:41:55 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Sep 20, 2025):

Sounds like you need to get into contact with PikaPods and ask them to increase the file upload size limit. You can also try "reset sync" from the settings page in Actual after making a backup to see if that helps.

<!-- gh-comment-id:3314917823 --> @matt-fidd commented on GitHub (Sep 20, 2025): Sounds like you need to get into contact with PikaPods and ask them to increase the file upload size limit. You can also try "reset sync" from the settings page in Actual after making a backup to see if that helps.
GiteaMirror commented 2026-04-10 19:41:56 -05:00
Author
Owner
Copy Link

@hamza-zafar-319 commented on GitHub (Sep 20, 2025):

I am seeing the same error message pop up. I get the error in an incognito window as well. I am running Actual in a Docker container. I'm on my phone, I'll investigate more when I get to my computer.

Edit: update. Restarting the Docker container fixed it 🤷

<!-- gh-comment-id:3315040347 --> @hamza-zafar-319 commented on GitHub (Sep 20, 2025): I am seeing the same error message pop up. I get the error in an incognito window as well. I am running Actual in a Docker container. I'm on my phone, I'll investigate more when I get to my computer. Edit: update. Restarting the Docker container fixed it 🤷
GiteaMirror commented 2026-04-10 19:41:56 -05:00
Author
Owner
Copy Link

@kcollett commented on GitHub (Sep 21, 2025):

[...] You can also try "reset sync" from the settings page in Actual after making a backup to see if that helps.

Even after reading the docs at https://actualbudget.org/docs/getting-started/sync#what-does-resetting-sync-mean, I'm a little unclear on which computer I should use "reset sync". (The document writers were perhaps wishcasting when they say "Actual will always guide you through this." All that really happens is a popup that instructs the user to open a bug.) I think what the docs are saying is to use "reset sync" on the computer that has the correct data; is that correct?

<!-- gh-comment-id:3315909273 --> @kcollett commented on GitHub (Sep 21, 2025): > [...] You can also try "reset sync" from the settings page in Actual after making a backup to see if that helps. Even after reading the docs at https://actualbudget.org/docs/getting-started/sync#what-does-resetting-sync-mean, I'm a little unclear on which computer I should use "reset sync". (The document writers were perhaps wishcasting when they say "Actual will always guide you through this." All that really happens is a popup that instructs the user to open a bug.) I _think_ what the docs are saying is to use "reset sync" on the computer that has the correct data; is that correct?
GiteaMirror commented 2026-04-10 19:41:57 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Sep 21, 2025):

[...] You can also try "reset sync" from the settings page in Actual after making a backup to see if that helps.

Even after reading the docs at https://actualbudget.org/docs/getting-started/sync#what-does-resetting-sync-mean, I'm a little unclear on which computer I should use "reset sync". (The document writers were perhaps wishcasting when they say "Actual will always guide you through this." All that really happens is a popup that instructs the user to open a bug.) I think what the docs are saying is to use "reset sync" on the computer that has the correct data; is that correct?

Yes, that's correct. I'll have a read of the docs later on and see if there's scope to improve the wording there.

<!-- gh-comment-id:3315910770 --> @matt-fidd commented on GitHub (Sep 21, 2025): > > [...] You can also try "reset sync" from the settings page in Actual after making a backup to see if that helps. > > Even after reading the docs at https://actualbudget.org/docs/getting-started/sync#what-does-resetting-sync-mean, I'm a little unclear on which computer I should use "reset sync". (The document writers were perhaps wishcasting when they say "Actual will always guide you through this." All that really happens is a popup that instructs the user to open a bug.) I _think_ what the docs are saying is to use "reset sync" on the computer that has the correct data; is that correct? Yes, that's correct. I'll have a read of the docs later on and see if there's scope to improve the wording there.
GiteaMirror commented 2026-04-10 19:41:57 -05:00
Author
Owner
Copy Link

@kcollett commented on GitHub (Sep 21, 2025):

[...]

Yes, that's correct. I'll have a read of the docs later on and see if there's scope to improve the wording there.

Thank you. I gave that a go, but on the machine with the out-of-sync data I'm running into the Request Entity Too Large issue I ran into above. I'll contact the PikaPods folks to see what can be done.

Update: For reference, the PikaPods support team sent me this in responce to my query:

This error is occurring because the size of the data you're trying to synchronize is larger than the pod's configured limit. You can increase this limit by changing the environment variable ACTUAL_UPLOAD_FILE_SYNC_SIZE_LIMIT_MB.

You can update this environment variable from your pod settings by navigating to Settings > ENV VARS.

I changed the value of that environment variable from the default of 20 to 25, and that seemed to resolve the problem. (I did close my AB window and relaunch the pod; I'm not sure if that was absolutely necessary.)

<!-- gh-comment-id:3315919596 --> @kcollett commented on GitHub (Sep 21, 2025): > [...] > > Yes, that's correct. I'll have a read of the docs later on and see if there's scope to improve the wording there. Thank you. I gave that a go, but on the machine with the out-of-sync data I'm running into the Request Entity Too Large issue I ran into above. I'll contact the PikaPods folks to see what can be done. Update: For reference, the PikaPods support team sent me this in responce to my query: > This error is occurring because the size of the data you're trying to synchronize is larger than the pod's configured limit. You can increase this limit by changing the environment variable ACTUAL_UPLOAD_FILE_SYNC_SIZE_LIMIT_MB. > You can update this environment variable from your pod settings by navigating to Settings > ENV VARS. I changed the value of that environment variable from the default of 20 to 25, and that seemed to resolve the problem. (I did close my AB window and relaunch the pod; I'm not sure if that was absolutely necessary.)
GiteaMirror commented 2026-04-10 19:41:58 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Sep 24, 2025):

[...]
Yes, that's correct. I'll have a read of the docs later on and see if there's scope to improve the wording there.

Thank you. I gave that a go, but on the machine with the out-of-sync data I'm running into the Request Entity Too Large issue I ran into above. I'll contact the PikaPods folks to see what can be done.

Update: For reference, the PikaPods support team sent me this in responce to my query:

This error is occurring because the size of the data you're trying to synchronize is larger than the pod's configured limit. You can increase this limit by changing the environment variable ACTUAL_UPLOAD_FILE_SYNC_SIZE_LIMIT_MB.

You can update this environment variable from your pod settings by navigating to Settings > ENV VARS.

I changed the value of that environment variable from the default of 20 to 25, and that seemed to resolve the problem. (I did close my AB window and relaunch the pod; I'm not sure if that was absolutely necessary.)

Glad you got it sorted!

<!-- gh-comment-id:3326046242 --> @matt-fidd commented on GitHub (Sep 24, 2025): > > [...] > > Yes, that's correct. I'll have a read of the docs later on and see if there's scope to improve the wording there. > > Thank you. I gave that a go, but on the machine with the out-of-sync data I'm running into the Request Entity Too Large issue I ran into above. I'll contact the PikaPods folks to see what can be done. > > Update: For reference, the PikaPods support team sent me this in responce to my query: > > > This error is occurring because the size of the data you're trying to synchronize is larger than the pod's configured limit. You can increase this limit by changing the environment variable ACTUAL_UPLOAD_FILE_SYNC_SIZE_LIMIT_MB. > > > You can update this environment variable from your pod settings by navigating to Settings > ENV VARS. > > I changed the value of that environment variable from the default of 20 to 25, and that seemed to resolve the problem. (I did close my AB window and relaunch the pod; I'm not sure if that was absolutely necessary.) Glad you got it sorted!
GiteaMirror commented 2026-04-10 19:41:58 -05:00
Author
Owner
Copy Link

@gregbtm commented on GitHub (Nov 7, 2025):

Same issue here, same errors. Docker container.

Trying to sync from imported csv - logs chock full of payload too large messages. The env vars for file size limits are already at 100mb.

Will keep trying :/

<!-- gh-comment-id:3500206146 --> @gregbtm commented on GitHub (Nov 7, 2025): Same issue here, same errors. Docker container. Trying to sync from imported csv - logs chock full of payload too large messages. The env vars for file size limits are already at 100mb. Will keep trying :/
GiteaMirror commented 2026-04-10 19:41:59 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Nov 7, 2025):

Same issue here, same errors. Docker container.

Trying to sync from imported csv - logs chock full of payload too large messages. The env vars for file size limits are already at 100mb.

Will keep trying :/

How big is the csv? Can you try "reset sync" in the settings page?

<!-- gh-comment-id:3504376717 --> @matt-fidd commented on GitHub (Nov 7, 2025): > Same issue here, same errors. Docker container. > > Trying to sync from imported csv - logs chock full of payload too large messages. The env vars for file size limits are already at 100mb. > > Will keep trying :/ How big is the csv? Can you try "reset sync" in the settings page?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#9423
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?