It appears that the initial search did not yield relevant documentation about the specific database retention period in the self-hosted solution for Prefect. I will attempt another search with queries that may be more focused on the configuration and management of the database in a self-hosted Prefect deployment.
Let's refine our search.
The documentation does not provide information about a specific retention period for data in the database for self-hosted Prefect solutions. Instead, it outlines how to configure and use databases with Prefect, including resetting the database with Prefect Server.
If you're looking for a retention policy, this may be something you need to configure manually within your chosen database (e.g., PostgreSQL) or through the management of your self-hosted infrastructure. This would typically involve setting up retention policies, periodic clean-up tasks, or archiving strategies based on your requirements.
For details about using and configuring databases with a self-hosted Prefect Server, please refer to the
documentation. Note that the database can be reset using the following CLI command, which will clear all data and reapply the schema:
prefect server database reset -y
However, please be aware that this will completely clear the database and is not a retention policy. For detailed management and retention, you would need to configure these settings within the database itself or within your infrastructure management tools.