-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Bug: Syncs can become "stale" in the DB and are never cleared out #2015
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Found and updated the image (f8d6456), but it didnt fix the existing issue. UPD:
The UI also throws an error - Here, I`ve manualy set an account balance from the previous reported in the original message which lead to the error above. Here i repeated the same and got the same error: UPD2: got the same errors when adding a transaction as well "Content missing" text in the UI:
|
Hey @FluffyClaws, this appears to be related to the recent breaking changes we pushed. Have you gone through the migration guide? You'll need to add the Redis service to your Compose stack as described here: |
Hi @zachgoll , I'm having same issue, just added redis, but still stuck syncing accounts. ![]() |
Turns out sidekiq worker wasn't running so I updated my start command to run it. Although, it doesn't seem to be updating the investments section, and syncing the stock prices. And the "Syncing accounts data" alert still gets stuck sometimes |
Error Logs
|
Oh well, I really did miss it. Thanks for quick reply and help! |
Just want to leave a note, in case someone else runs in that issue: |
I followed the tutorial to upgrade, and the upgrade process was all normal, but I still get stuck with the "Syncing accounts data..." prompt. |
Same here. I have Redis on Heroku and works fine. If I manually sync an account the prompt disappears, but when I navigate to the home, transactions or budget, appears again.
|
I have the same issue. I found that manually syncing accounts remove the "Syncing accounts data..." until a page refresh, except for the investments account with holdings. The holding value is not updated since 21st of March with the synth values (I have token left) |
@rubenRP thanks for the logs, those are helpful. Based on those logs and other comments, it appears that the syncs are working fine (indicating that Redis is working fine with the queue backend). My guess is that there are some leftover Lines 62 to 69 in 8e6b81a
I'm wondering if we need to just push a simple migration that clears out "pending" syncs that are stale. For those experiencing the issue, it would be helpful to see the following query results: -- Query 1: sync counts
SELECT
status,
COUNT(*) as sync_count
FROM syncs
GROUP by status;
-- Query 2: most recent syncs
SELECT
syncable_type,
last_ran_at,
status
FROM syncs
ORDER BY last_ran_at DESC; |
@zachgoll Attached the result of the queries: |
@jakubkottnauer @rubenRP thanks for those query results. Very helpful. This is exactly what I suspected—when everyone did the migration, there were likely "auto-syncs" that triggered to run, got queued up in the DB, then were unable to actually execute because the GoodJob process was no longer running. So now, users have Deleting those sync records should fix this. I'm thinking we need to implement some "cleanup" mechanism so that when syncs are triggered daily, it clears out any "stale" syncs (i.e. syncs that are not |
Same issues here |
Hello, While doing my recent PR #2081, I discovered a bug related to the Donut loading animation. The recent update to Tailwind v4 removed the keyframe animation from the Donut component, which is necessary to trigger the Although this issue is not directly related to the Syncing notification (since it doesn't use the Donut loading animation), I thought it was worth mentioning. |
Before you start (required)
General checklist
How are you using Maybe?
Self hoster checklist
If you are a self-hosted user, please complete all of the information below. Issues with incomplete information will be marked as
Needs Info
to help our small team prioritize bug fixes.Bug description
Got stuck with "Syncing accounts data..." job. The balances are not being updated anymore, though i can add\remove\modify new\existing transactions. Not 100% sure, but it might have occured after clicking "Sycn account", althoug Im not even sure about functionality of it, since the only connected thing is Synth API.
This issue persists across all of the "accounts".
Restarting / recreating the container didnt help, and I dont see any errors or even warns in the logs.
To Reproduce
Steps to reproduce the behavior:
No clue, but a good starting point could be this:
Expected behavior
After adding a new transactions the balance is updating.
Screenshots and/or recordings
Also attaching the logs:
The text was updated successfully, but these errors were encountered: