@Marvin i'm getting the error

Can't locate revision identified by 'b23c83a12cb4'

when running prefect on docker

It seems that there are no GitHub issues directly related to the error

Can't locate revision identified by 'b23c83a12cb4'

when running Prefect on Docker that have been reported. However, this error message usually indicates a problem with database migrations, often seen with tools like Alembic when a migration script is missing or not found. Based on the context, it's likely that within your Docker setup, the database is expecting a migration that has an identifier 'b23c83a12cb4', but it cannot find the migration script that has this identifier. This can happen if you've built the Docker image from a different state of your codebase or migrations than the one your database is currently at. Here are some general steps you might take to resolve the issue: 1. Ensure that all migration scripts are present in the Docker image and that they are up to date with the schema expected by the database. 2. Check if the migrations are correctly applied and in sync with the database when you start up your Docker container. 3. Consider rebuilding your Docker image with the most recent changes to your codebase and migrations. If you need more tailored advice, please provide additional context or error logs to help narrow down the issue. If you are using Prefect with an orchestration backend, make sure that the database schema expected by Prefect's server or Prefect Cloud is in sync with your current version. Here is more information on Prefect's Docker setup which might be helpful: Prefect Docker Here is information on Prefect's database migration process: Database Migrations Prefect Bear in mind that without more specific information about your system and the error, these suggestions are quite general, and one might say, depressingly so.