[Bug]: #2230

Closed
opened 2026-02-28 20:07:28 -06:00 by GiteaMirror · 8 comments
Owner

Originally created by @JJOCSAK on GitHub (Jun 26, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

A bug happeWhen trying to add an entry I get an error and it will not add the entry.
The error:

Something internally went wrong. You may want to restart the app
if anything looks wrong. Please report this as a new issue on GutHub.

Restarting did not fix the issue.

I tried on my phone and another PC but get the same error.
Yesterday worked everything worked fine.

I can start the app but not finish entering anything.ned!

How can we reproduce the issue?

How can we reproduce the issue?

Where are you hosting Actual?

None

What browsers are you seeing the problem on?

No response

Operating System

None

Originally created by @JJOCSAK on GitHub (Jun 26, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? A bug happeWhen trying to add an entry I get an error and it will not add the entry. The error: Something internally went wrong. You may want to restart the app if anything looks wrong. Please report this as a new issue on GutHub. Restarting did not fix the issue. I tried on my phone and another PC but get the same error. Yesterday worked everything worked fine. I can start the app but not finish entering anything.ned! ### How can we reproduce the issue? How can we reproduce the issue? ### Where are you hosting Actual? None ### What browsers are you seeing the problem on? _No response_ ### Operating System None
GiteaMirror added the needs infobug labels 2026-02-28 20:07:28 -06:00
Author
Owner

@youngcw commented on GitHub (Jun 26, 2025):

can you open the browser console and see what errors it shows? Open the console by pressing ctrl-shift-I

@youngcw commented on GitHub (Jun 26, 2025): can you open the browser console and see what errors it shows? Open the console by pressing ctrl-shift-I
Author
Owner

@JJOCSAK commented on GitHub (Jun 26, 2025):

Where in the console would the error be?

Sent with Proton Mail secure email.

On Thursday, June 26th, 2025 at 11:17 AM, youngcw @.***> wrote:

youngcw left a comment (actualbudget/actual#5237)

can you open the browser console and see what errors it shows? Open the console by pressing ctrl-shift-I


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@JJOCSAK commented on GitHub (Jun 26, 2025): Where in the console would the error be? Sent with [Proton Mail](https://proton.me/mail/home) secure email. On Thursday, June 26th, 2025 at 11:17 AM, youngcw ***@***.***> wrote: > youngcw left a comment [(actualbudget/actual#5237)](https://github.com/actualbudget/actual/issues/5237#issuecomment-3008857324) > > can you open the browser console and see what errors it shows? Open the console by pressing ctrl-shift-I > > — > Reply to this email directly, [view it on GitHub](https://github.com/actualbudget/actual/issues/5237#issuecomment-3008857324), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BUACCPYSBZ7D6VUEA6YYIC33FQFHPAVCNFSM6AAAAACAGRCOFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMBYHA2TOMZSGQ). > You are receiving this because you authored the thread.Message ID: ***@***.***>
Author
Owner

@JJOCSAK commented on GitHub (Jun 26, 2025):

Where in the console would the error be?

@JJOCSAK commented on GitHub (Jun 26, 2025): Where in the console would the error be?
Author
Owner

@youngcw commented on GitHub (Jun 26, 2025):

If you are looking at the console, the error should be a big red box

@youngcw commented on GitHub (Jun 26, 2025): If you are looking at the console, the error should be a big red box
Author
Owner

@JJOCSAK commented on GitHub (Jun 26, 2025):

This is the only error I see:
Server Log: [Exception] ClockDriftError: maximum clock drift exceeded 1750960863962 1750952091765 300000

If I open another older file that seems to work normally.

@JJOCSAK commented on GitHub (Jun 26, 2025): This is the only error I see: Server Log: [Exception] ClockDriftError: maximum clock drift exceeded 1750960863962 1750952091765 300000 If I open another older file that seems to work normally.
Author
Owner

@youngcw commented on GitHub (Jun 26, 2025):

That error means you picked up a timezone shift or something similar. I don't know why it would work for one file and not the other

@youngcw commented on GitHub (Jun 26, 2025): That error means you picked up a timezone shift or something similar. I don't know why it would work for one file and not the other
Author
Owner

@JJOCSAK commented on GitHub (Jun 26, 2025):

How do I fix it?

@JJOCSAK commented on GitHub (Jun 26, 2025): How do I fix it?
Author
Owner

@JJOCSAK commented on GitHub (Jun 26, 2025):

I fixed it.
I did a "Reset Sync"

@JJOCSAK commented on GitHub (Jun 26, 2025): I fixed it. I did a "Reset Sync"
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2230