@Marvin I’m getting this error on downgrade when doing the prefect server reset:

sqlalchemy.exc.IntegrityError: (sqlalchemy.dialects.postgresql.asyncpg.IntegrityError) <class 'asyncpg.exceptions.NotNullViolationError'>: column "flow_run_id" of relation "task_run" contains null values
[SQL: ALTER TABLE task_run ALTER COLUMN flow_run_id SET NOT NULL]
(Background on this error at: <https://sqlalche.me/e/20/gkpj>)
An exception occurred.
error: Recipe `reset-prefect` failed on line 22 with exit code 1

It seems you're experiencing a database integrity issue during a downgrade operation in Prefect. The error indicates that the

flow_run_id

column in the

task_run

table contains null values, which violates a NOT NULL constraint. This issue has been reported by others, and it typically arises when attempting to reset the Prefect server or database. Here are some steps you might consider to resolve this: 1. Backup Data: If possible, back up any important data before proceeding with more drastic measures. 2. Database Inspection: Inspect your database to identify any rows in the

task_run

table where

flow_run_id

is null. You might need to manually update or delete these rows to satisfy the NOT NULL constraint. 3. Fresh Environment: If you aim to have a completely fresh environment, you might consider fully dropping and recreating the database. This is a more aggressive approach but ensures that no old data or constraints interfere with the setup. 4. Check for Updates: Ensure you are using the latest version of Prefect, as updates may contain fixes for such issues. You can check the latest release notes here. 5. Community Help: If the issue persists, consider reaching out to the Prefect community or forums where other users and developers might offer additional insights or workarounds. For future reference, you can follow the related GitHub issue here for any updates or similar cases. If you need more specific guidance on any of these steps, feel free to ask!