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 #5010] [Bug]: problem synching my budget after updating it #51259

New Issue
Closed
opened 2026-04-30 17:16:44 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-30 17:16:44 -05:00
Owner
Copy Link

Originally created by @BlissfullyP on GitHub (May 17, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5010

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

A bug happened! Whenever I click sync it gives me an error saying it cannot and to create a issue using Github

How can we reproduce the issue?

Click on synch and it will give an error saying the changes has failed to synch to create an issue

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Safari

Operating System

Mac OSX

Originally created by @BlissfullyP on GitHub (May 17, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5010 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? A bug happened! Whenever I click sync it gives me an error saying it cannot and to create a issue using Github ### How can we reproduce the issue? Click on synch and it will give an error saying the changes has failed to synch to create an issue ### Where are you hosting Actual? Pikapods ### What browsers are you seeing the problem on? Safari ### Operating System Mac OSX
GiteaMirror added the needs infobug labels 2026-04-30 17:16:44 -05:00
GiteaMirror commented 2026-04-30 17:16:52 -05:00
Author
Owner
Copy Link

@alecbakholdin commented on GitHub (May 17, 2025):

Please send a screenshot of your console logs (cmd + shift + I and then click the "console" tab). That should give us an indication of where to look.

<!-- gh-comment-id:2888445254 --> @alecbakholdin commented on GitHub (May 17, 2025): Please send a screenshot of your console logs (cmd + shift + I and then click the "console" tab). That should give us an indication of where to look.
GiteaMirror commented 2026-04-30 17:16:55 -05:00
Author
Owner
Copy Link

@rjross227 commented on GitHub (Jun 3, 2025):

I've got the same issue, I cleared the console, then hit Sync, and then grabbed this screenshot.

Image

I googled Clock Time Drift Error, the results got me thinking about just re-syncing my computer clock with the com.apple.time server so I opened System Preferences, and then Date and Time and then toggled the "set automatically" on both the date and the time pages.
I went back to Actual and clicked Sync and the issue was solved.
I typed out my process in case it helps anyone else.
Cheers

<!-- gh-comment-id:2933582914 --> @rjross227 commented on GitHub (Jun 3, 2025): I've got the same issue, I cleared the console, then hit Sync, and then grabbed this screenshot. ![Image](https://github.com/user-attachments/assets/b50c1309-8030-44b3-ae66-d100043c5a6e) I googled Clock Time Drift Error, the results got me thinking about just re-syncing my computer clock with the com.apple.time server so I opened System Preferences, and then Date and Time and then toggled the "set automatically" on both the date and the time pages. I went back to Actual and clicked Sync and the issue was solved. I typed out my process in case it helps anyone else. Cheers
GiteaMirror commented 2026-04-30 17:16:56 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jun 3, 2025):

@BlissfullyP can you verify if the above solution helped solve the problem for you?

<!-- gh-comment-id:2936860249 --> @MatissJanis commented on GitHub (Jun 3, 2025): @BlissfullyP can you verify if the above solution helped solve the problem for you?
GiteaMirror commented 2026-04-30 17:16:56 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 11, 2025):

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.

<!-- gh-comment-id:2961020489 --> @github-actions[bot] commented on GitHub (Jun 11, 2025): 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
tech-support
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#51259
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?