PrefectHQ/prefect 2.14.21

on GitHub

Release 2.14.21

Introducing work queue status

We're excited to unveil the new status indicators for work queues in Prefect's UI, enhancing your ability to oversee and control flow run execution within our hybrid work pools.

Work queues will now display one of three distinct statuses:

• Ready - one or more online workers are actively polling the work queue
• Not Ready - no online workers are polling the work queue, signaling a need for intervention
• Paused - the work queue is intentionally paused, preventing execution

With the introduction of work queue status, you'll notice the absence of deprecated work queue health indicators in the UI.

See the documentation on work queue status for more information.

For now, this is an experimental feature, and can be enabled by running:

prefect config set PREFECT_EXPERIMENTAL_ENABLE_WORK_QUEUE_STATUS=True

See the following pull request for implementation details:
- #11829

Fixes

• Remove unnecessary WARNING level log indicating a task run completed successfully — #11810
• Fix a bug where block placeholders declared in pull steps of the deployments section of a prefect.yaml file were not resolved correctly — #11740
• Use pool_pre_ping to improve stability for long-lived PostgreSQL connections — #11911

Documentation

• Clarify Docker tutorial code snippet to ensure commands are run from the correct directory — #11833
• Remove beta tag from incident documentation and screenshots — #11921
• Update Prefect Cloud account roles docs to reflect renaming of previous "Admin" role to "Owner" and creation of new "Admin" role that cannot bypass SSO — #11925

Experimental

• Ensure task subscribers can only pick up task runs they are able to execute — #11805
• Allow a task server to reuse the same task runner to speed up execution — #11806
• Allow configuration of maximum backlog queue size and maximum retry queue size for autonomous task runs — #11825

All changes: 2.14.20...2.14.21