Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

<@ULVA73B9P> Will the prefect timeout feature clean up after the task or subflow times out?

It looks like the Prefect API has multiple settings that can help you with the timeout feature. The setting `PREFECT_API_DATABASE_TIMEOUT` replaces the deprecated setting `PREFECT_ORION_DATABASE_TIMEOUT` and allows you to set a timeout for database connection. Additionally, the setting `PREFECT_API_DATABASE_CONNECTION_TIMEOUT` replaces the deprecated setting `PREFECT_ORION_DATABASE_CONNECTION_TIMEOUT` and sets the connection timeout for database connections. 

The Prefect API reference "prefect.client.orchestration" has an `httpx_settings` method that can set a timeout with a `timeout` keyword argument. This argument requires a `connect`, `read`, and `write` value to be set, all of which are set to the value of the parameter `PREFECT_API_REQUEST_TIMEOUT`. The `pool` parameter can also be set, with a default value of 25.

This information was found in the Prefect API reference "prefect.client.orchestration" and in the Prefect API reference "prefect.settings". I hope this helps you understand the timeout feature and answer your question.