Skip to content

Conversation

@flippedcoder
Copy link
Contributor

@flippedcoder flippedcoder commented Dec 17, 2025

What does this PR do?

This adds a new page to explain Task Queue priority and fairness.

@vercel
Copy link

vercel bot commented Dec 17, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
temporal-documentation Ready Ready Preview, Comment Jan 21, 2026 2:04pm

Request Review

@github-actions
Copy link
Contributor

github-actions bot commented Dec 17, 2025

📖 Docs PR preview links

[Task Queue Priority](#task-queue-priority) and [Task Queue Fairness](#task-queue-fairness) are two ways to manage the distribution of work within Task Queues. Priority focuses on how Tasks are prioritized within a Task Queue and Fairness aims to prevent one set of prioritized Tasks from blocking others within the same Task Queue.

:::tip Support, stability, and dependency info
Priority and Fairness is currently in [pre-release](/evaluate/development-production-features/release-stages#pre-release).
Copy link
Contributor Author

@flippedcoder flippedcoder Jan 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think these docs will go live when we do the public preview release. Will confirm with @bchav .


If you're using Temporal Cloud, contact Temporal Support or your Temporal account team to enable this feature for your cloud Namespaces.

If you're self-hosting Temporal, use the latest pre-release development server and set `matching.useNewMatcher` to `true` in the [dynamic config](https://github.com/temporalio/temporal/blob/a3a53266c002ae33b630a41977274f8b5b587031/common/dynamicconfig/constants.go#L1345-L1348) on the relevant Task Queues or Namespaces.
Copy link
Contributor Author

@flippedcoder flippedcoder Jan 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bchav Just checking if this is accurate or not.


When you use Worker Versioning and you're moving Workflows from one version to another, the ordering of Workflow Tasks that are moved to the next version is undefined. Tasks redirected to a new Worker version may not be treated fairly with respect to each other or Tasks that aren't redirected.

There isn't a limit on the number of fairness keys you can use, but their accuracy can degrade as you add more.
Copy link
Contributor Author

@flippedcoder flippedcoder Jan 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bchav Do we want to include a number here? Like the accuracy doesn't degrade until ~100,000 or something?

Copy link
Contributor

@lennessyy lennessyy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In addition to this page, I think these options should also be called out in the individual SDKs. We can just link to this page, but if they are not called out there then developers who only look at their language-specific resources will not find this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants