prefect · Issues· 861 open

prefect deploy ignores explicit schedules: [], retaining an active schedule (3.8.5)

Two tests don't check what their names say: composite trigger does_not_act and subflow pause

Flow ends COMPLETED when it returns a list of .map() results containing a FAILED task (states nested one level are ignored)

Mapped children not yet started leave no task run when PrefectFutureList.result() raises the first failure

`db_vacuum` on high-volume Postgres: events and flow_runs contend for one hardcoded connection, and row DELETE cannot promptly reduce disk usage

mark_deployments_ready updates every deployment on a queue on every worker poll

Add Quick Run and Custom Run to the flow's Deployments tab

PostgreSQL /flow_runs/filter times out for state-filtered START_TIME_ASC queries on large flow_run tables

Allow List vs Deny List for ACLs

Renovate Dependency Dashboard

Zombie-detection automation false-positives on healthy completed flows

Add a new way to consume logs

Support custom log storage implementations

prefect-redis: ephemeral consumer loops on `no such key` when trimming a missing Redis stream

`dbt source freshness` logs are not associated with the enclosing task