You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/concepts/task-completion.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ The completion-time resolver already has higher-precedence sources:
19
19
2. The active main session bucket (most useful, but can be retargeted)
20
20
3. The task's stored `delivery` config (can be partial or stale)
21
21
22
-
When all three lose the outbound target, the resolver falls back to the route leasekeyed by `run_id`. The lease is keyed by `run_id`rather than `task_id` because a single task may produce multiple runs over time, and each run owns its own delivery origin.
22
+
When all three lose the outbound target, the resolver falls back to the route lease. The lease is keyed by the `(run_id, runtime, scope_kind, owner_key, child_session_key)` tuple — the same scope facts the task registry uses to disambiguate shared-runId task records. The lease is keyed by that 5-tuple rather than `task_id` because a single task may produce multiple runs over time, and each run owns its own delivery origin within its scope.
0 commit comments