github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Bug]: Problem syncing changes #2558

New Issue
Closed
opened 2026-02-28 20:18:58 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-02-28 20:18:58 -06:00
Owner
Copy Link

Originally created by @kcollett on GitHub (Oct 21, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

The app reports "We had problems syncing your changes." It additionally asked me to open a bug report.

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

Windows 11

Originally created by @kcollett on GitHub (Oct 21, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? The app reports "We had problems syncing your changes." It additionally asked me to open a bug report. ### 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 Windows 11
GiteaMirror added the bugneeds info labels 2026-02-28 20:18:58 -06:00
GiteaMirror commented 2026-02-28 20:18:59 -06:00
Author
Owner
Copy Link

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

Note: Resetting the sync ID on the other, known good instance did not fix this.

@kcollett commented on GitHub (Oct 21, 2025): Note: Resetting the sync ID on the other, known good instance did **not** fix this.
GiteaMirror commented 2026-02-28 20:18:59 -06:00
Author
Owner
Copy Link

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

Hey, are you able to provide reproduction instructions please?
If so, please could you provide the logs from the browser console (https://appuals.com/open-browser-console/)

@matt-fidd commented on GitHub (Oct 21, 2025): Hey, are you able to provide reproduction instructions please? If so, please could you provide the logs from the browser console (https://appuals.com/open-browser-console/)
GiteaMirror commented 2026-02-28 20:18:59 -06:00
Author
Owner
Copy Link

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

I do see some lots of these:

> PostError: PostError: <!DOCTYPE html>
> <html lang="en">
> <head>
> <meta charset="utf-8">
> <title>Error</title>
> </head>
> <body>
> <pre>Payload Too Large</pre>
> </body>
> </html>
> 
>     at throwIfNot200 (post.ts:32:11)
>     at post.ts:212:17
>     at async _fullSync (index.ts:671:9)
>     at async index.ts:561:5
>     at async app.ts:20:3
@kcollett commented on GitHub (Oct 21, 2025): I do see some lots of these: ``` > PostError: PostError: <!DOCTYPE html> > <html lang="en"> > <head> > <meta charset="utf-8"> > <title>Error</title> > </head> > <body> > <pre>Payload Too Large</pre> > </body> > </html> > > at throwIfNot200 (post.ts:32:11) > at post.ts:212:17 > at async _fullSync (index.ts:671:9) > at async index.ts:561:5 > at async app.ts:20:3 ```
GiteaMirror commented 2026-02-28 20:19:00 -06:00
Author
Owner
Copy Link

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

In terms of reproducing, I'm not doing anything at all; the problem simply arises when the app tries to sync with the server. (Were you seriously expecting something different?)

@kcollett commented on GitHub (Oct 21, 2025): In terms of reproducing, I'm not doing anything at all; the problem simply arises when the app tries to sync with the server. (Were you seriously expecting something different?)
GiteaMirror commented 2026-02-28 20:19:00 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Oct 21, 2025):

You need to go to your pika pods settings and change the environment variable for max upload size. Make it be larger than what is there now. A safe bet would be to double the value

@youngcw commented on GitHub (Oct 21, 2025): You need to go to your pika pods settings and change the environment variable for max upload size. Make it be larger than what is there now. A safe bet would be to double the value
GiteaMirror commented 2026-02-28 20:19:01 -06:00
Author
Owner
Copy Link

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

What is the exact name of the environment variable you are referring to? I see ACTUAL_UPLOAD_FILE_SYNC_LIMIT_MB and ACTUAL_UPLOAD_FILE_SIZE_LIMIT_MB. (I imagine it's the former since it has "SYNC" in it, but I just want to make sure. Also, it looks like I've previously set that variable to 25 (perhaps as a result of another sync issue).)

@kcollett commented on GitHub (Oct 21, 2025): What is the exact name of the environment variable you are referring to? I see ACTUAL_UPLOAD_FILE_SYNC_LIMIT_MB and ACTUAL_UPLOAD_FILE_SIZE_LIMIT_MB. (I imagine it's the former since it has "SYNC" in it, but I just want to make sure. Also, it looks like I've previously set that variable to 25 (perhaps as a result of another sync issue).)
GiteaMirror commented 2026-02-28 20:19:01 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Oct 21, 2025):

You can increase both

@youngcw commented on GitHub (Oct 21, 2025): You can increase both
GiteaMirror commented 2026-02-28 20:19:01 -06:00
Author
Owner
Copy Link

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

OK, I set ACTUAL_UPLOAD_FILE_SYNC_LIMIT_MB to 50 and ACTUAL_UPLOAD_FILE_SIZE_LIMIT_MB to 40 (since the default value was 20, so 2X is 40). Afterwards, there was a very long sync that resulted in the message that occurs when the sync ID has been reset; after reverting to the server version (i.e. the state from the known good instance), the sync completed normally.

@kcollett commented on GitHub (Oct 21, 2025): OK, I set ACTUAL_UPLOAD_FILE_SYNC_LIMIT_MB to 50 and ACTUAL_UPLOAD_FILE_SIZE_LIMIT_MB to 40 (since the default value was 20, so 2X is 40). Afterwards, there was a very long sync that resulted in the message that occurs when the sync ID has been reset; after reverting to the server version (i.e. the state from the known good instance), the sync completed normally.
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
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug needs info
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#2558
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?