Open
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
zzstoatzz
changed the title
zzstoatzz
requested review from
chrisguidry,
cicdw and
desertaxle
as code owners
desertaxle
approved these changes
Apr 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR clarifies the
prefect-daskdocs around Dask task priorities.Why
The current example can be read as implying that a later high-priority
.submit()call will reorder execution ahead of earlier low-priority submissions. In practice, Dask priority is a soft scheduling hint for queued work and does not preempt tasks that have already been assigned to a worker.Impact
Readers should have a more accurate expectation of how
dask.annotate(priority=...)behaves when used withDaskTaskRunner.Root cause
The behavior discussed in #21568 is not caused by Prefect overriding Dask annotations. A local repro against a real Prefect OSS server showed that the annotations reach Dask, while execution may still begin in submission order for already-assigned work.
Validation
curl http://localhost:4200/api/healthuv run prefect config viewuv run --extra dask python repros/21568.py