mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-09 11:42:54 -05:00
[Bug]: Database is out of sync with migrations #1176
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#1176
Reference in New Issue
Block a user
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?
Originally created by @totalitarian on GitHub (Jun 27, 2024).
Verified issue does not already exist?
What happened?
Fresh install of 24.6 and I get this error
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Microsoft Edge
Operating System
Linux
@youngcw commented on GitHub (Jun 27, 2024):
did you use the edge build at some point? or use a different desktop client than the one on the release page?
@youngcw commented on GitHub (Jun 27, 2024):
The easy fix probably is to update your server to edge until the next release comes through
@totalitarian commented on GitHub (Jun 27, 2024):
I did use edge at one point. So what i'm trying to do now is start completely from fresh but I keep getting references to My-Finances-347c8aa somehow
@totalitarian commented on GitHub (Jun 27, 2024):
I tried going back to edge but still get the same issue
@youngcw commented on GitHub (Jun 27, 2024):
if you are trying to start from scratch make sure you clear your browser cache and delete all the server files
@totalitarian commented on GitHub (Jun 27, 2024):
Just tried that. This is my landing page on actual
But still get this error even after cache reset
We had an unknown problem opening “My-Finances-347c8aa”
I'm at a loss how it can still think My-Finances-347c8aa exists...
@youngcw commented on GitHub (Jun 27, 2024):
Maybe try changing the ip:port or url to kinda force everything to go away. Also that old budget file could have resynced to the server before the error, so check that
@youngcw commented on GitHub (Jun 27, 2024):
one thing that helps is to use an incognito window so that way nothing is stored in your browser. That can help narrow down which side is remembering things
@totalitarian commented on GitHub (Jun 27, 2024):
Sorry to be a pain but i've cleared caches, installed actual on another server, ip:port and only used incognito. I'm totally baffled now...
@youngcw commented on GitHub (Jun 27, 2024):
🤷 Something must be holding onto data
@totalitarian commented on GitHub (Jun 27, 2024):
Managed to fix it. I had to clear cache on my iphone, ipad and PC. Got there in the end and thank you for your patience
@TFenby commented on GitHub (Jul 27, 2024):
This issue has cropped up on my install, and I've only ever used the Docker image of
docker.io/actualbudget/actual-server:latestIs it possible an edge build got tagged as latest or something?
Specifically, this is happening when I try using your (youngcw) fork of actualplaid. Or does that utility keep its own database that would be the source of that error? I can open a ticket over there if that's the case.
Edit: I'm guessing the actual node module included w/ that actualplaid utility is just behind on available migrations, since the one that is says is missing (1716359441000) is indeed part of the latest release. I'll open an issue in your other repo.