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

[Bug]: we had problems syncing your changes #2639

New Issue
Closed
opened 2026-02-28 20:22:38 -06:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-02-28 20:22:38 -06:00
Owner
Copy Link

Originally created by @es20001 on GitHub (Nov 20, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Getting a message on all devices, we had problems syncing your changes, please report a GitHub issue.
Getting this error for several days.

How can we reproduce the issue?

Not sure.

Where are you hosting Actual?

None

What browsers are you seeing the problem on?

No response

Operating System

None

Originally created by @es20001 on GitHub (Nov 20, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Getting a message on all devices, we had problems syncing your changes, please report a GitHub issue. Getting this error for several days. ### How can we reproduce the issue? Not sure. ### Where are you hosting Actual? None ### What browsers are you seeing the problem on? _No response_ ### Operating System None
GiteaMirror added the bugneeds info labels 2026-02-28 20:22:38 -06:00
GiteaMirror commented 2026-02-28 20:22:39 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Nov 20, 2025):

👋 How can we reproduce the issue?

Without specific instructions (i.e. access to your server or the budget file export) - there is nothing much we can do to help here.

@MatissJanis commented on GitHub (Nov 20, 2025): 👋 How can we reproduce the issue? Without specific instructions (i.e. access to your server or the budget file export) - there is nothing much we can do to help here.
GiteaMirror commented 2026-02-28 20:22:39 -06:00
Author
Owner
Copy Link

@baileyr9350 commented on GitHub (Nov 22, 2025):

I have this issue hosting on Pikapods, using firefox on windows 11. I can open my own ticket if needed, but given that it's the same error message I'm trying not to duplicate. I've had this issue for a long time. It seems to mostly occur if I've been using Actual on another computer (windows 11 still, but vivaldi as the browser). It happens the other way around as well - i.e. I used Actual on my desktop, then later tried to open it on the laptop.

@baileyr9350 commented on GitHub (Nov 22, 2025): I have this issue hosting on Pikapods, using firefox on windows 11. I can open my own ticket if needed, but given that it's the same error message I'm trying not to duplicate. I've had this issue for a long time. It seems to mostly occur if I've been using Actual on another computer (windows 11 still, but vivaldi as the browser). It happens the other way around as well - i.e. I used Actual on my desktop, then later tried to open it on the laptop.
GiteaMirror commented 2026-02-28 20:22:40 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Nov 22, 2025):

@baileyr9350 can you provide a way for us to reproduce the issue? Nothing we can do without a reproduction.

@MatissJanis commented on GitHub (Nov 22, 2025): @baileyr9350 can you provide a way for us to reproduce the issue? Nothing we can do without a reproduction.
GiteaMirror commented 2026-02-28 20:22:40 -06:00
Author
Owner
Copy Link

@baileyr9350 commented on GitHub (Nov 22, 2025):

@MatissJanis

Here's what I think is causing it for me, so I don't know if you have a way to do this, but this is all I know enough about to suggest. I'm not a developer (at least not for stuff like this, I do some data science at work) so I don't really know what else to provide.

  1. Use Actual (hosted via PikaPods) on one browser, make some changes, leave file open & browser open.
  2. Go to Actual (new instance) on other brower & system and see if the bug pops up

If you can direct me to where I can get more info about what's happening in the error, I'm happy to do that -- if there's some way to inspect the network responses, or see a more detailed error. I don't know what to look for on my own, though. I think saying "Nothing we can do without a reproduction" is maybe an oversimplification... I would think there's at least somewhere in the code that handles errors in the first place, and that might be a good place to check and make some educated guesses on what I can try, places I might be able to look to provide more info, etc.

@baileyr9350 commented on GitHub (Nov 22, 2025): @MatissJanis Here's what I think is causing it for me, so I don't know if you have a way to do this, but this is all I know enough about to suggest. I'm not a developer (at least not for stuff like this, I do some data science at work) so I don't really know what else to provide. 1. Use Actual (hosted via PikaPods) on one browser, make some changes, leave file open & browser open. 2. Go to Actual (new instance) on other brower & system and see if the bug pops up If you can direct me to where I can get more info about what's happening in the error, I'm happy to do that -- if there's some way to inspect the network responses, or see a more detailed error. I don't know what to look for on my own, though. I think saying "Nothing we can do without a reproduction" is maybe an oversimplification... I would think there's at least somewhere in the code that handles errors in the first place, and that might be a good place to check and make some educated guesses on what I can try, places I might be able to look to provide more info, etc.
GiteaMirror commented 2026-02-28 20:22:41 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Nov 22, 2025):

@baileyr9350 this is the "catch all" error case. It happens in unexpected scenarios.

You can open the dev console and see if any error message is printed there. That might help debug it slightly more.

But again.. this is the unexpected error scenario. So there's not much guesswork we can do here. The bast way we could help here is if we would be able to reproduce it.

I use Actual on ~3 different devices and have never had this error.

@MatissJanis commented on GitHub (Nov 22, 2025): @baileyr9350 this is the "catch all" error case. It happens in unexpected scenarios. You can open the dev console and see if any error message is printed there. That _might_ help debug it slightly more. But again.. this is the unexpected error scenario. So there's not much guesswork we can do here. The bast way we could help here is if we would be able to reproduce it. I use Actual on ~3 different devices and have never had this error.
GiteaMirror commented 2026-02-28 20:22:41 -06:00
Author
Owner
Copy Link

@baileyr9350 commented on GitHub (Nov 22, 2025):

Restarting my Pod tends to fix it, which is what I did today, so now I'm not getting the error anymore. But next time I get it I'll try to pull up the dev console and see what's there.

I'm trying to think of other details that might help recreate it. Typically I'm updating actual ~once every 2 weeks. I'll tend to leave the window open on one computer or the other, and then I think this issue is happening when I go to open it on the other computer a couple weeks later with that "stagnant" window still open on the original computer.

A couple weeks ago I updated my budget on my laptop and left the window open. Knowing I tend to get this error in this scenario, I went to my laptop first and opened up the Actual window with the goal of closing out of it completely. It popped up the "loading" screen and stayed stuck there. I ended up restarting the pod so that I could work it on my desktop, since the changes I'd made on my laptop weren't showing up on my desktop and I was getting the sync error. Once my pod restarted, my desktop instance had the changes I'd made a couple weeks ago and the sync error was no longer showing up.

@baileyr9350 commented on GitHub (Nov 22, 2025): Restarting my Pod tends to fix it, which is what I did today, so now I'm not getting the error anymore. But next time I get it I'll try to pull up the dev console and see what's there. I'm trying to think of other details that might help recreate it. Typically I'm updating actual ~once every 2 weeks. I'll tend to leave the window open on one computer or the other, and then I think this issue is happening when I go to open it on the other computer a couple weeks later with that "stagnant" window still open on the original computer. A couple weeks ago I updated my budget on my laptop and left the window open. Knowing I tend to get this error in this scenario, I went to my laptop first and opened up the Actual window with the goal of closing out of it completely. It popped up the "loading" screen and stayed stuck there. I ended up restarting the pod so that I could work it on my desktop, since the changes I'd made on my laptop weren't showing up on my desktop and I was getting the sync error. Once my pod restarted, my desktop instance had the changes I'd made a couple weeks ago and the sync error was no longer showing up.
GiteaMirror commented 2026-02-28 20:22:41 -06:00
Author
Owner
Copy Link

@es20001 commented on GitHub (Nov 23, 2025):

Found my problem, my pod was closed because auto-repayment was off. Would
be great to get an error like "can't connect to pod"
Thank you for the response 🙂

On Thu, Nov 20, 2025, 23:15 Matiss Janis Aboltins @.***>
wrote:

MatissJanis left a comment (actualbudget/actual#6210)
https://github.com/actualbudget/actual/issues/6210#issuecomment-3560077241

👋 How can we reproduce the issue?

Without specific instructions (i.e. access to your server or the budget
file export) - there is nothing much we can do to help here.

—
Reply to this email directly, view it on GitHub
https://github.com/actualbudget/actual/issues/6210#issuecomment-3560077241,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH64XP7IQUKWXOAY5II2W3D35YVQVAVCNFSM6AAAAACMUYNT66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNRQGA3TOMRUGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@es20001 commented on GitHub (Nov 23, 2025): Found my problem, my pod was closed because auto-repayment was off. Would be great to get an error like "can't connect to pod" Thank you for the response 🙂 On Thu, Nov 20, 2025, 23:15 Matiss Janis Aboltins ***@***.***> wrote: > *MatissJanis* left a comment (actualbudget/actual#6210) > <https://github.com/actualbudget/actual/issues/6210#issuecomment-3560077241> > > 👋 How can we reproduce the issue? > > Without specific instructions (i.e. access to your server or the budget > file export) - there is nothing much we can do to help here. > > — > Reply to this email directly, view it on GitHub > <https://github.com/actualbudget/actual/issues/6210#issuecomment-3560077241>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AH64XP7IQUKWXOAY5II2W3D35YVQVAVCNFSM6AAAAACMUYNT66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNRQGA3TOMRUGE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
GiteaMirror commented 2026-02-28 20:22:42 -06:00
Author
Owner
Copy Link

@lmsteffan commented on GitHub (Nov 29, 2025):

I also got, and solved in my case, the same error. As I host the Actualbudget server on my own site I was able to investigate.
Nginx refused the request to sync because "body size was too large".
IIn order to decrease the file size I performed a sync request, and after that it worked.

Should you need more details (logs, network traces, console output...) please tell me.

@lmsteffan commented on GitHub (Nov 29, 2025): I also got, and solved in my case, the same error. As I host the Actualbudget server on my own site I was able to investigate. Nginx refused the request to sync because "body size was too large". IIn order to decrease the file size I performed a sync request, and after that it worked. Should you need more details (logs, network traces, console output...) please tell me.
GiteaMirror commented 2026-02-28 20:22:42 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Dec 8, 2025):

Closing. OP found the problem.

@youngcw commented on GitHub (Dec 8, 2025): Closing. OP found the problem.
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#2639
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?