Skip to content

Add Task Queue Priority and Worker Versioning as alternatives in task-routing docs #4328

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
Copilot wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Add Task Queue Priority and Worker Versioning as alternatives in task-routing docs #4328

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ca51032
Initial plan
Copilot Mar 24, 2026
e30f876
Add Task Queue Priority and Worker Versioning mentions to task-routin…
Copilot Mar 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/encyclopedia/workers/task-routing-worker-sessions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,12 +85,18 @@ In this case, each type of box would have its own Task Queue and a Workflow can

If your use case involves more than one priority, you can create one Task Queue per priority, with a Worker pool per priority.

Alternatively, you can use [Task Queue Priority](/develop/task-queue-priority-fairness), which lets you assign priority levels to Tasks within a single Task Queue.
This approach avoids the overhead of managing multiple Task Queues and separate Worker pools while still ensuring higher-priority Tasks are processed first.

### Versioning

Task Routing is the simplest way to version your code.

If you have a new backward-incompatible Activity Definition, start by using a different Task Queue.

Alternatively, you can use [Worker Versioning](/worker-versioning), which lets you tag Workers with a version and route Workflow and Activity Tasks to specific versions without requiring separate Task Queues.
Worker Versioning supports both Pinned Workflows (which complete on a single Worker Deployment Version) and Auto-Upgrade Workflows (which automatically move to the latest version).

## What is a Worker Session? {#worker-session}

A Worker Session is a feature provided by some SDKs that provides a straightforward API for [Task Routing](#task-routing) to ensure that Activity Tasks are executed with the same Worker without requiring you to manually specify Task Queue names.
Expand Down