Repository navigation
Document fixed workflow-start time and durable wait patterns - #169
Merged
Merged
Conversation
|
This was referenced Oct 20, 2026
rmcdaniel
marked this pull request as ready for review
October 20, 2026 09:19
Member
Author
|
Published portal acceptance is now verified for this interim documentation correction.
This documents the currently released fixed-start behavior. It does not deliver an advancing replay clock: .github #215 remains OPEN, and Website #302 remains superseded by that product feature. No new runtime or qualification phase was needed; all task runtime/dependency/raw state remains retired. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Change
Interim released-behavior clarification for shared #215, alongside Website #307. Website #302 has been superseded by the actual advancing replay-safe clock requirement.
Document Python 2.6.1's current fixed run-start
ctx.now(), successor-run anchors, persisted timestamp precedence, missing-clock diagnostics, durable timers/Server deadlines and sequence-based event ordering. Preserve the currently released #146 behavior in this docs-only PR; #215 owns the new advancing clock and replay-compatible migration.Only
docs/sdk-reference.mdchanges. No runtime, dependency, protocol or version change, and no claim of normalized cross-SDK clocks.Verification
a28a4b585269ccca2643cf0a8dd82ae6a4800625a53ffa1940c5e85df12865aamatches the immutable release.General retains merge and portal-publication acceptance. Publishing this clarification does not complete shared #215.