DashboardopencodeSessionExecution lease fencing

SessionExecution lease fencing

Category: preference
Confidence: 1.00
ID: 01a0af08-7b1b-73e9-a7c2-70a95ec2eac2
Project ID: c0425955-02bc-4c17-9af2-b114c00077e7
Cross-project: No
Recalled in other projects: 0
Source session: 0gn8mvDqdnbuGUBog
Created: 2026-09-15 01:18:15
Updated: 2026-09-17 11:02:43

Content

Always fence Session execution with durable (sessionID, executionID, ownerID) leases, never process-local ownership. Ordinary acquisition must neither start a second owner during a live lease, re-enter its own uncertain live lease, nor overwrite an expired lease; only recovery may take eligible expired work, never cancellation-phase or superseded work. Exact-owner, unexpired predicates must guard renewal, mutation, publication, dispatch, settlement, cleanup, quarantine, and recovery. Every fenced write requires exactly one affected row; stale work must not overwrite cancellation, emit side effects, revive expiry, or delete successor state.

Move to: