github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-10 23:54:00 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #4713] [Bug]: On repo migration from v25.2.1 and v.25.3.1, a last reconciled ID 1740506588539 are added to __migration__ #116375

New Issue
Closed
opened 2026-06-11 09:38:23 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-06-11 09:38:23 -05:00
Owner
Copy Link

Originally created by @cnshing on GitHub (Mar 31, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4713

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Specifically, this causes imports to fail:

migrations.ts:152 Database is out of sync with migrations: ObjectappliedIds: Array(42)0: 15489579706271: 15506015986482: 15557861943283: 15617518335104: 15676995527275: 15823841635736: 15977565664487: 16086525960438: 16086525960449: 161262554823610: 161478263933611: 161574596794812: 161616701079613: 161897517735814: 163257148901215: 167972886704016: 168111503384517: 168297483813818: 168500787684219: 168613966086620: 168874952727321: 168884123800022: 169123339600023: 169443875200024: 169704624000025: 170457202373026: 170457202373127: 170726703300028: 171278452300029: 171635944100030: 172031058600031: 172066486724132: 172066500000033: 172271760100034: 172280401900035: 172366556500036: 173074418200037: 173664000000038: 173715840000039: 173849145200040: 173913955000041: 1740506588539length: 42[[Prototype]]: Array(0)available: Array(41)0: "1548957970627_remove-db-version.sql"1: "1550601598648_payees.sql"2: "1555786194328_remove_category_group_unique.sql"3: "1561751833510_indexes.sql"4: "1567699552727_budget.sql"5: "1582384163573_cleared.sql"6: "1597756566448_rules.sql"7: "1608652596043_parent_field.sql"8: "1608652596044_trans_views.sql"9: "1612625548236_optimize.sql"10: "1614782639336_trans_views2.sql"11: "1615745967948_meta.sql"12: "1616167010796_accounts_order.sql"13: "1618975177358_schedules.sql"14: "1632571489012_remove_cache.js"15: "1679728867040_rules_conditions.sql"16: "1681115033845_add_schedule_name.sql"17: "1682974838138_remove_payee_rules.sql"18: "1685007876842_add_category_hidden.sql"19: "1686139660866_remove_account_type.sql"20: "1688749527273_transaction_filters.sql"21: "1688841238000_add_account_type.sql"22: "1691233396000_add_schedule_next_date_tombstone.sql"23: "1694438752000_add_goal_targets.sql"24: "1697046240000_add_reconciled.sql"25: "1704572023730_add_account_sync_source.sql"26: "1704572023731_add_missing_goCardless_sync_source.sql"27: "1707267033000_reports.sql"28: "1712784523000_unhide_input_group.sql"29: "1716359441000_include_current.sql"30: "1720310586000_link_transfer_schedules.sql"31: "1720664867241_add_payee_favorite.sql"32: "1720665000000_goal_context.sql"33: "1722717601000_reports_move_selected_categories.js"34: "1722804019000_create_dashboard_table.js"35: "1723665565000_prefs.js"36: "1730744182000_fix_dashboard_table.sql"37: "1736640000000_custom_report_sorting.sql"38: "1737158400000_add_learn_categories_to_payees.sql"39: "1738491452000_sorting_rename.sql"40: "1739139550000_bank_sync_page.sql"length: 41[[Prototype]]: Array(0)[[Prototype]]: Object

The 2nd last element for both arrays are identically indexed, which means the missing culprit must be the last element, 1740506588539.

I am not familiar enough with the codebase to know if it is intended for the migration check to purposely ignore this ID, or whether the export database function fails to include it, or whether my particular instance included this data when it wasn't supposed to, because exporting the test budget from http://demo.actualbudget.lan also exhibits this problem from both the serverless client and my self hosted server.

Fix:
What worked for me was removing the offending row from db.sqlite and re-importing. Alternatively, copying the migrations data to any instance seems to work for that particular instance. I will also do some investigation and try to resolve this bug next week if I have free time.

How can we reproduce the issue?

  1. Follow the migration steps from https://actualbudget.org/docs/actual-server-repo-move/ from

Q. I Build from source. How do I keep up to date?

  1. Export data from the latest instance

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Chrome

Operating System

Linux

Originally created by @cnshing on GitHub (Mar 31, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4713 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Specifically, this causes imports to fail: ```Typescript migrations.ts:152 Database is out of sync with migrations: ObjectappliedIds: Array(42)0: 15489579706271: 15506015986482: 15557861943283: 15617518335104: 15676995527275: 15823841635736: 15977565664487: 16086525960438: 16086525960449: 161262554823610: 161478263933611: 161574596794812: 161616701079613: 161897517735814: 163257148901215: 167972886704016: 168111503384517: 168297483813818: 168500787684219: 168613966086620: 168874952727321: 168884123800022: 169123339600023: 169443875200024: 169704624000025: 170457202373026: 170457202373127: 170726703300028: 171278452300029: 171635944100030: 172031058600031: 172066486724132: 172066500000033: 172271760100034: 172280401900035: 172366556500036: 173074418200037: 173664000000038: 173715840000039: 173849145200040: 173913955000041: 1740506588539length: 42[[Prototype]]: Array(0)available: Array(41)0: "1548957970627_remove-db-version.sql"1: "1550601598648_payees.sql"2: "1555786194328_remove_category_group_unique.sql"3: "1561751833510_indexes.sql"4: "1567699552727_budget.sql"5: "1582384163573_cleared.sql"6: "1597756566448_rules.sql"7: "1608652596043_parent_field.sql"8: "1608652596044_trans_views.sql"9: "1612625548236_optimize.sql"10: "1614782639336_trans_views2.sql"11: "1615745967948_meta.sql"12: "1616167010796_accounts_order.sql"13: "1618975177358_schedules.sql"14: "1632571489012_remove_cache.js"15: "1679728867040_rules_conditions.sql"16: "1681115033845_add_schedule_name.sql"17: "1682974838138_remove_payee_rules.sql"18: "1685007876842_add_category_hidden.sql"19: "1686139660866_remove_account_type.sql"20: "1688749527273_transaction_filters.sql"21: "1688841238000_add_account_type.sql"22: "1691233396000_add_schedule_next_date_tombstone.sql"23: "1694438752000_add_goal_targets.sql"24: "1697046240000_add_reconciled.sql"25: "1704572023730_add_account_sync_source.sql"26: "1704572023731_add_missing_goCardless_sync_source.sql"27: "1707267033000_reports.sql"28: "1712784523000_unhide_input_group.sql"29: "1716359441000_include_current.sql"30: "1720310586000_link_transfer_schedules.sql"31: "1720664867241_add_payee_favorite.sql"32: "1720665000000_goal_context.sql"33: "1722717601000_reports_move_selected_categories.js"34: "1722804019000_create_dashboard_table.js"35: "1723665565000_prefs.js"36: "1730744182000_fix_dashboard_table.sql"37: "1736640000000_custom_report_sorting.sql"38: "1737158400000_add_learn_categories_to_payees.sql"39: "1738491452000_sorting_rename.sql"40: "1739139550000_bank_sync_page.sql"length: 41[[Prototype]]: Array(0)[[Prototype]]: Object ``` The 2nd last element for both arrays are identically indexed, which means the missing culprit must be the last element, `1740506588539`. I am not familiar enough with the codebase to know if it is intended for the migration check to purposely ignore this ID, or whether the export database function fails to include it, or whether my particular instance included this data when it wasn't supposed to, because exporting the test budget from `http://demo.actualbudget.lan` also exhibits this problem from both the serverless client and my self hosted server. Fix: What worked for me was removing the offending row from `db.sqlite` and re-importing. Alternatively, copying the migrations data to any instance seems to work for that particular instance. I will also do some investigation and try to resolve this bug next week if I have free time. ### How can we reproduce the issue? 1. Follow the migration steps from https://actualbudget.org/docs/actual-server-repo-move/ from > Q. I [Build from source](https://actualbudget.org/docs/install/build-from-source). How do I keep up to date? 2. Export data from the latest instance ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Chrome ### Operating System Linux
GiteaMirror added the bug label 2026-06-11 09:38:23 -05:00
GiteaMirror commented 2026-06-11 09:38:26 -05:00
Author
Owner
Copy Link

@cnshing commented on GitHub (Apr 5, 2025):

With release v25.4.0 and PR #4459, new repo migrations from v25.2.1 to the latest will include 1740506588539 in available ids. This should prevent the out of sync issue for future versions.

<!-- gh-comment-id:2780623717 --> @cnshing commented on GitHub (Apr 5, 2025): With release v25.4.0 and PR #4459, new repo migrations from v25.2.1 to the latest will include `1740506588539` in available ids. This should prevent the out of sync issue for future versions.
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
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
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#116375
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?