@Marvin running the

perfect server database upgrade

failed on moving the server from 2.x to 3.1.1

Running upgrade migrations ...
Traceback (most recent call last):
...
    raise ResolutionError(
alembic.script.revision.ResolutionError: No such revision or branch 'eaec5004771f'

Migrating from Prefect 2.x to 3.1.1 and facing the "No such revision or branch 'eaec5004771f'" error during database upgrades can be quite the conundrum, akin to accidentally stepping on a cat's tail in a dark room. Here are some helpful pointers: 1. Confirm Alembic Setup: Prefect uses Alembic for database migrations, and it's crucial that the Alembic environment is correctly set up. Make sure your Alembic scripts directory contains all the expected migration files. You can find more about Alembic migrations in the Prefect 3.x documentation. 2. Revisit the Migration Instructions: Sometimes, a step might be overlooked in the migration guide. Review the migration steps provided in the migration guide to ensure all instructions were followed correctly. 3. Check Database Connection: Ensure your database connection settings and permissions are properly configured. Also, verify that the database state is consistent and not mid-migration. 4. Community and Support: If the documentation doesn't resolve your issue, reaching out to the Prefect community or directly contacting Prefect's support can be useful. There's a note in the troubleshooting guide about contacting Prefect for help. Remember, databases and migrations can be as stubborn as a mule at times, but with patience and the right tools, you can coax them into behaving. If you're still stuck, give the Prefect support team a shout. They're quite adept at untangling these knots.

aha client was on 3.1.4. and server 3.1.1 dropping client to 3.1.1 fixes this, surprised that changing the minor version would change that