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

[BUG] Sync error with scheduled transaction #120

New Issue
Closed
opened 2026-02-28 18:49:12 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 18:49:12 -06:00
Owner
Copy Link

Originally created by @shall0pass on GitHub (Aug 17, 2022).

A Sync error can be created when following the steps below. Changing the system date of the PC is meant to simulate a longer length of time. This was done on a PC where the server and web browsers were local, so the system time affects all components equally.

  1. Create a new budget.
  2. Add an account and one scheduled transaction that does not auto insert.
  3. Sync two browsers to the budget. (I used Brave and Firefox)
  4. Close one of the browsers (I closed Firefox)
  5. Manually advance the computers date to the next scheduled transaction.
  6. Refresh "primary browser" and post the transaction.
  7. Manually advance the computers date to the next scheduled transaction date.
  8. Refresh "primary browser and post the transaction.
  9. Open second browser again.
  10. Sync error

I had 3 total transactions in this test. One for the initial account creation and two for scheduled transaction postings.

This issue was initially discussed on Discord in the #server-setup channel.

Originally created by @shall0pass on GitHub (Aug 17, 2022). A Sync error can be created when following the steps below. Changing the system date of the PC is meant to simulate a longer length of time. This was done on a PC where the server and web browsers were local, so the system time affects all components equally. 1. Create a new budget. 2. Add an account and one scheduled transaction that does not auto insert. 3. Sync two browsers to the budget. (I used Brave and Firefox) 4. Close one of the browsers (I closed Firefox) 5. Manually advance the computers date to the next scheduled transaction. 6. Refresh "primary browser" and post the transaction. 7. Manually advance the computers date to the next scheduled transaction date. 8. Refresh "primary browser and post the transaction. 9. Open second browser again. 10. Sync error I had 3 total transactions in this test. One for the initial account creation and two for scheduled transaction postings. This issue was initially discussed on Discord in the #server-setup channel.
GiteaMirror commented 2026-02-28 18:49:12 -06:00
Author
Owner
Copy Link

@TomAFrench commented on GitHub (Sep 2, 2022):

Potentially closed by https://github.com/actualbudget/actual-server/pull/75

@TomAFrench commented on GitHub (Sep 2, 2022): Potentially closed by https://github.com/actualbudget/actual-server/pull/75
GiteaMirror commented 2026-02-28 18:49:13 -06:00
Author
Owner
Copy Link

@rich-howell commented on GitHub (Oct 17, 2022):

Marking as fixed as we are no longer able to replicate.

@rich-howell commented on GitHub (Oct 17, 2022): Marking as fixed as we are no longer able to replicate.
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
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#120
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?