github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-12 01:52:09 -05:00
Code Issues 1.6k Packages Projects Releases 57 Wiki Activity

[Bug]: This file is not a cloud file for multi-users #2880

New Issue
Closed
opened 2026-02-28 20:31:25 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 20:31:25 -06:00
Owner
Copy Link

Originally created by @yoyotogblo on GitHub (Feb 1, 2026).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

My wife and I both update our budget using different computers. I use a Surface PC, she uses an Apple Macbook Pro.

Whenever either of us (person A) edits and syncs the budget on our PC and the other person (person B) opens up Actual Budget on their computer, Actual syncs all the changes on person B's PC. However, once Actual loads up, we always get the error "This file is not a cloud file" and a new budget file would have been created. Person B then needs to close the file and redownload the synced file and open that. Otherwise the budget would go out of sync between the 2 users.

We're self-hosting Actual Budget in a LXC container on a mini PC running Proxmox. However, we always had this same issue when hosting on fly.io.

How can we reproduce the issue?

Person A updates synced budget on their PC
Person B opens Actual and it downloads Person A's updates
Person B's Actual Budget creates a new file and complains that it's not a cloud file

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Desktop App (Electron)

Operating System

Windows 11

Originally created by @yoyotogblo on GitHub (Feb 1, 2026). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? My wife and I both update our budget using different computers. I use a Surface PC, she uses an Apple Macbook Pro. Whenever either of us (person A) edits and syncs the budget on our PC and the other person (person B) opens up Actual Budget on their computer, Actual syncs all the changes on person B's PC. However, once Actual loads up, we always get the error "This file is not a cloud file" and a new budget file would have been created. Person B then needs to close the file and redownload the synced file and open that. Otherwise the budget would go out of sync between the 2 users. We're self-hosting Actual Budget in a LXC container on a mini PC running Proxmox. However, we always had this same issue when hosting on fly.io. ### How can we reproduce the issue? Person A updates synced budget on their PC Person B opens Actual and it downloads Person A's updates Person B's Actual Budget creates a new file and complains that it's not a cloud file ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Desktop App (Electron) ### Operating System Windows 11
GiteaMirror added the bugneeds info labels 2026-02-28 20:31:25 -06:00
GiteaMirror commented 2026-02-28 20:31:26 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Feb 2, 2026):

When you say "downloads Person A's updates", do you have to redownload the file every time? The new file stuff sounds like your data isn't being persisted

@youngcw commented on GitHub (Feb 2, 2026): When you say "downloads Person A's updates", do you have to redownload the file every time? The new file stuff sounds like your data isn't being persisted
GiteaMirror commented 2026-02-28 20:31:26 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 10, 2026):

This issue has been automatically closed because there have been no comments for 7 days after the "needs info" label was added. If you still need help, please feel free to reopen the issue with the requested information.

@github-actions[bot] commented on GitHub (Feb 10, 2026): This issue has been automatically closed because there have been no comments for 7 days after the "needs info" label was added. If you still need help, please feel free to reopen the issue with the requested information.
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#2880
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?