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

[GH-ISSUE #5930] [Bug]: duplicate budget "for all devices" #9481

New Issue
Closed
opened 2026-04-10 19:45:34 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-10 19:45:34 -05:00
Owner
Copy Link

Originally created by @Unmarked6660 on GitHub (Oct 15, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5930

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

A bug happened!

I duplicated my budget for all devices (locally has its own annoying nag about not being in sync.)
I use this to test my budget for the next month ahead of time. Sync becomes a red warning triangle at the top of the page, and the banner keeps appearing at the bottom right "We had problems syncing your changes, please report this as a bug by opening a github issue.."

I tried ignoring this for the last week but today I'm all in submission mode.

I'm using docker for the server. In this case I am testing using my browser, not the electron app.

How can we reproduce the issue?

How can we reproduce the issue?

Duplicate a budget, selecting all devices (not just locally.). Make some deposit transactions for Income to play with the budget. Bam! I feel bad, I did not search and find an existing issue because if this was an existing issue, someone would certainly have resolved it already. Sorry! <3

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Safari

Operating System

Mac OSX

Originally created by @Unmarked6660 on GitHub (Oct 15, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5930 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? A bug happened! I duplicated my budget for all devices (locally has its own annoying nag about not being in sync.) I use this to test my budget for the next month ahead of time. Sync becomes a red warning triangle at the top of the page, and the banner keeps appearing at the bottom right "We had problems syncing your changes, please report this as a bug by opening a github issue.." I tried ignoring this for the last week but today I'm all in submission mode. I'm using docker for the server. In this case I am testing using my browser, not the electron app. ### How can we reproduce the issue? How can we reproduce the issue? Duplicate a budget, selecting all devices (not just locally.). Make some deposit transactions for Income to play with the budget. Bam! I feel bad, I did not search and find an existing issue because if this was an existing issue, someone would certainly have resolved it already. Sorry! <3 ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Safari ### Operating System Mac OSX
GiteaMirror added the bug label 2026-04-10 19:45:34 -05:00
GiteaMirror commented 2026-04-10 19:45:36 -05:00
Author
Owner
Copy Link

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

Could you try resetting the sync ID in the settings?

<!-- gh-comment-id:3410909831 --> @matt-fidd commented on GitHub (Oct 16, 2025): Could you try resetting the sync ID in the settings?
GiteaMirror commented 2026-04-10 19:45:37 -05:00
Author
Owner
Copy Link

@Unmarked6660 commented on GitHub (Oct 16, 2025):

tl;dr That seems to have resolved it! Thank you!

Robert

Long version:
I am selecting Switch file, Duplicate budget new name “testing” duplicate for all devices. Selecting the testing budget. Going to settings, advanced, clicking Reset Sync (should this section be moved up to be included with Sync ID: ?)

Before:
Budget ID: testing-f957266
Sync ID: cb8f34dd-56b4-49b5-9649-9e74c931121c

After:
Budget ID: testing-f957266 (same)
Sync ID: a045073d-8464-4bf6-a53a-c4a44dae77bc

Now I’ll do the same testing I’ve done recently before generating the bug report

Seems good!

On Oct 16, 2025, at 09:32, Matt Fiddaman @.***> wrote:

matt-fidd
left a comment
(actualbudget/actual#5930)
https://github.com/actualbudget/actual/issues/5930#issuecomment-3410909831
Could you try resetting the sync ID in the settings?

—
Reply to this email directly, view it on GitHub https://github.com/actualbudget/actual/issues/5930#issuecomment-3410909831, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJOJHGVOBZIIUMTN7BPZIK33X6NAVAVCNFSM6AAAAACJJQUJYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMJQHEYDSOBTGE.
You are receiving this because you authored the thread.

<!-- gh-comment-id:3411166274 --> @Unmarked6660 commented on GitHub (Oct 16, 2025): tl;dr That seems to have resolved it! Thank you! Robert Long version: I am selecting Switch file, Duplicate budget new name “testing” duplicate for all devices. Selecting the testing budget. Going to settings, advanced, clicking Reset Sync (should this section be moved up to be included with Sync ID: ?) Before: Budget ID: testing-f957266 Sync ID: cb8f34dd-56b4-49b5-9649-9e74c931121c After: Budget ID: testing-f957266 (same) Sync ID: a045073d-8464-4bf6-a53a-c4a44dae77bc Now I’ll do the same testing I’ve done recently before generating the bug report Seems good! > On Oct 16, 2025, at 09:32, Matt Fiddaman ***@***.***> wrote: > > > matt-fidd > left a comment > (actualbudget/actual#5930) > <https://github.com/actualbudget/actual/issues/5930#issuecomment-3410909831> > Could you try resetting the sync ID in the settings? > > — > Reply to this email directly, view it on GitHub <https://github.com/actualbudget/actual/issues/5930#issuecomment-3410909831>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJOJHGVOBZIIUMTN7BPZIK33X6NAVAVCNFSM6AAAAACJJQUJYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMJQHEYDSOBTGE>. > You are receiving this because you authored the thread. >
GiteaMirror commented 2026-04-10 19:45:38 -05:00
Author
Owner
Copy Link

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

I've not seen this before and I can't seem to replicate it but the file should set up its sync automatically when you "duplicate for everyone". If it gets itself stuck then resetting the sync will usually do the trick.

<!-- gh-comment-id:3411193094 --> @matt-fidd commented on GitHub (Oct 16, 2025): I've not seen this before and I can't seem to replicate it but the file should set up its sync automatically when you "duplicate for everyone". If it gets itself stuck then resetting the sync will usually do the trick.
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
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#9481
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?