anon28410
anon28410β€’2w ago

Amazing to have continued updates. Sadly

Amazing to have continued updates. Sadly ran into a migration error on my relatively new instance. Seems like a simple thing to fix.
convex-backend-1 | 2025-05-24T01:01:42.649056Z INFO model::migrations: Attempting migration
convex-backend-1 | 2025-05-24T01:01:42.649202Z INFO model::migrations: Migrating to 119
convex-backend-1 | 2025-05-24T01:01:42.649322Z ERROR model::migrations: Migration worker failed, sleeping 64.362319946s
convex-backend-1 | 2025-05-24T01:01:42.649398Z ERROR common::errors: Caught error (RUST_BACKTRACE=1 RUST_LOG=info,common::errors=debug for full trace): No next run found
convex-backend-1 | 2025-05-24T01:01:42.649056Z INFO model::migrations: Attempting migration
convex-backend-1 | 2025-05-24T01:01:42.649202Z INFO model::migrations: Migrating to 119
convex-backend-1 | 2025-05-24T01:01:42.649322Z ERROR model::migrations: Migration worker failed, sleeping 64.362319946s
convex-backend-1 | 2025-05-24T01:01:42.649398Z ERROR common::errors: Caught error (RUST_BACKTRACE=1 RUST_LOG=info,common::errors=debug for full trace): No next run found
Rolling back to the previous release seemed to work fine though πŸ‘
4 Replies
nipunn
nipunnβ€’2w ago
Rip. I’ll look into it in the next day or so. That’s no good! Glad rolling back worked I reproed it - working on a fix! Might happen today, might happen monday!
nipunn
nipunnβ€’5d ago
Hey @anon28410 - I just released again with a fix for the issue you were seeing! https://github.com/get-convex/convex-backend/commit/6ac741e135c08e236d709943a441dd98628b6037 was the fix if you are curious. It affected existing deployments that had cron jobs (crons.ts ) during upgrade.
GitHub
Separate model code+types for migration 119 (#37598) Β· get-convex/...
Grab the old version of Cron Jobs code from back when migr 119 itself ran. Bake it into history permanently. Will make sure migr always works. This is to allow us to keep releasing self-hosted and...
anon28410
anon28410OPβ€’5d ago
Super-duper, tested and migrated without any problems. πŸ‘ The new version also seems to behave more intelligently on startup, I previously would get lots of console errors while it was in the "bootstrapping" stage - now everything seems to wait until the backend is actually ready to receive requests. Thanks for fixing so quickly.
nipunn
nipunnβ€’5d ago
yep - there were hundreds of changes made by tens of engineers - lots of improvements since march!

Did you find this page helpful?