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

[GH-ISSUE #7106] [Bug]: Failed to download due to device time ( #28765

New Issue
Open
opened 2026-04-18 05:30:46 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-18 05:30:46 -05:00
Owner
Copy Link

Originally created by @elaske on GitHub (Mar 1, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7106

What happened?

I was trying to download the budget file on a computer after updating the docker to https://actualbudget.org/docs/releases#2621.

The browser gave me this error:

Image

Which corresponds to this PR: https://github.com/actualbudget/actual/pull/6789 solving this bug: https://github.com/actualbudget/actual/issues/3786

However, on the server:

Image

and the client:

Image

Console trace on a new attempt:

Image

NOTE: when allowing the budget to then load, it only shows in my case the "latest" transaction of December 8, 2025, which is almost 3 months old.

How can we reproduce the issue?

  1. Clear all budget data in browser (Cookies + Data)
  2. Log in
  3. Download budget on server.
  4. Wait - seems to also ask about Posting Scheduled transactions.
  5. Error message pops up.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 11

Originally created by @elaske on GitHub (Mar 1, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7106 ### What happened? I was trying to download the budget file on a computer after updating the docker to https://actualbudget.org/docs/releases#2621. The browser gave me this error: <img width="422" height="127" alt="Image" src="https://github.com/user-attachments/assets/4ae743bc-5a1a-4e4d-a40b-50780a28590a" /> Which corresponds to this PR: https://github.com/actualbudget/actual/pull/6789 solving this bug: https://github.com/actualbudget/actual/issues/3786 However, on the server: <img width="234" height="22" alt="Image" src="https://github.com/user-attachments/assets/4c9d2bc6-090d-4225-ab1b-f7c4cd13798c" /> and the client: <img width="805" height="149" alt="Image" src="https://github.com/user-attachments/assets/8068a495-efd1-4859-aafc-5e5004bf8ce8" /> Console trace on a new attempt: <img width="1343" height="976" alt="Image" src="https://github.com/user-attachments/assets/435d5479-aa2e-4071-a8e1-d20b1b88aa6a" /> NOTE: when allowing the budget to then load, it only shows in my case the "latest" transaction of December 8, 2025, which is almost 3 months old. ### How can we reproduce the issue? 1. Clear all budget data in browser (Cookies + Data) 2. Log in 3. Download budget on server. 4. Wait - seems to also ask about Posting Scheduled transactions. 5. Error message pops up. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 11
GiteaMirror added the tech debtbug labels 2026-04-18 05:30:46 -05:00
GiteaMirror commented 2026-04-18 05:30:48 -05:00
Author
Owner
Copy Link

@elaske commented on GitHub (Mar 1, 2026):

Digging into this further, I pulled a group-*.sqlite file off the server to investigate. I see that somehow there are entries into messages_binary that are in the future (2026-03-02T03:53:28.771Z-0000-ab5ccf5a6a1093b8 which a transaction posted earlier in the day was 2026-03-01T20:11:51.669Z-0007-a641d6b9574ce700).

Naively looking at these data, the Z normally would indicate UTC, but these are actually local time(s) to me in CDT. If that is the case, that means one of the CDT clients posted messages in the "future" which could be triggering the "time mismatch" error above.

<!-- gh-comment-id:3981237060 --> @elaske commented on GitHub (Mar 1, 2026): Digging into this further, I pulled a `group-*.sqlite` file off the server to investigate. I see that somehow there are entries into `messages_binary` that are in the future (`2026-03-02T03:53:28.771Z-0000-ab5ccf5a6a1093b8` which a transaction posted earlier in the day was `2026-03-01T20:11:51.669Z-0007-a641d6b9574ce700`). Naively looking at these data, the Z normally would indicate UTC, but these are actually local time(s) to me in CDT. If that is the case, that means one of the CDT clients posted messages in the "future" which could be triggering the "time mismatch" error above.
GiteaMirror commented 2026-04-18 05:30:48 -05:00
Author
Owner
Copy Link

@elaske commented on GitHub (Mar 3, 2026):

If this is just due to timestamps being from the "future", then it should have worked itself out by just waiting until AFTER those problematic timestamps happen. So, I waited until this evening to try again, with the steps to reproduce (including clear site data in between), and the error did not present itself again and I was able to download the budget file.

So a few things to suggest:

  1. Don't let the client set the timestamp in the database - and if you do, at least do so to a standard time reference, not what appears to be local time.
  2. The timestamps don't seem to be being checked for sync with the server on sending - this only appeared after items were added to the database with the "wrong" timestamp
  3. Recommend timestamping with the server time as the database consistency.
<!-- gh-comment-id:3987800893 --> @elaske commented on GitHub (Mar 3, 2026): If this is just due to timestamps being from the "future", then it should have worked itself out by just waiting until AFTER those problematic timestamps happen. So, I waited until this evening to try again, with the steps to reproduce (including clear site data in between), and the error did not present itself again and I was able to download the budget file. So a few things to suggest: 1. Don't let the client set the timestamp in the database - and if you do, at least do so to a standard time reference, not what appears to be local time. 2. The timestamps don't seem to be being checked for sync with the server on sending - this only appeared after items were added to the database with the "wrong" timestamp 3. Recommend timestamping with the server time as the database consistency.
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 tech debt
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#28765
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?