github-featured/triggerdotdev--trigger.dev
2
0
Fork 0
Code Issues Pull Requests Deployments Models Agent Notes Packages Projects Releases Wiki Activity

docs(run-engine): cut the ck fair scheduling release note down to the change

Browse Source 
The note ran to three sentences, advertised a server env var a user cannot set,
and described the pass-1 window degradation. .server-changes/README.md asks for a
one-line description of behaviour rather than implementation, and says that
needing a paragraph usually means you are describing the implementation.

Reported by Devin on #4367; this is its suggested wording.
This commit is contained in:
Wes Mason
2026-08-20 00:04:24 +01:00
parent 0c6992eb4a
commit 0128007ef1
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.server-changes/2026-07-24-ck-fair-scheduling.md
+1 -1
View File
@@ -3,4 +3,4 @@ area: webapp
type: feature
---
The run queue can now serve concurrency keys fairly, so one key with a large backlog no longer starves runs waiting on other keys. It is opt-in and off by default. While a lot of keys on the same queue are all waiting on retry backoffs or future start times, ordering falls back to arrival order until they clear, so runs keep flowing but the fairness guarantee is relaxed for that period.
One concurrency key with a large backlog no longer holds up runs waiting on other keys on the same queue.