Skip to content

Clarify timer SDK conformance boundary #140

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

Merged
rmcdaniel merged 1 commit into from
Sep 27, 2026
Merged

Clarify timer SDK conformance boundary #140

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 13 additions & 1 deletion conformance/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ CLI, PHP SDK, Python SDK, and Rust SDK tuple.
| SDK matrix | `durable-workflow/server`: PHP and Python published-artifact runners; `durable-workflow/sample-app`: `scripts/playground rust` |
| Search attributes | `durable-workflow/server`: `scripts/conformance/search-attributes-published-artifacts.sh` |
| Signals and queries | `durable-workflow/server`: `scripts/conformance/signals-queries-published-artifacts.sh` |
| Timers | `durable-workflow/server`: `scripts/conformance/timers-published-artifacts.sh` |
| Timers | `durable-workflow/server`: `scripts/conformance/timers-published-artifacts.sh` (embedded PHP workflow scenarios) |
| Worker versioning | `durable-workflow/server`: `scripts/conformance/worker-versioning-published-artifacts.sh` |
| Workflow lifecycle | `durable-workflow/server`: `scripts/conformance/workflow-lifecycle-published-artifacts.sh` |
| Workflow updates | `durable-workflow/server`: `scripts/conformance/workflow-updates-published-artifacts.sh` |
Expand Down Expand Up @@ -87,6 +87,18 @@ and workflow history. Report each direction's outcome and exact tuple
separately; these examples do not add a Rust shard to the Server runner or
prove cadence, restart, or failure recovery behavior.

The current
[timer scenario manifest](https://github.com/durable-workflow/server/blob/main/static/platform-conformance/timer-runtime-scenarios.json)
and published-artifact runner execute timer behavior in the Server image with
an embedded PHP workflow. The Python SDK artifact pin does not mean a Python
worker ran these scenarios; the runner does not require the PHP or Rust SDK
artifacts. Published PHP, Python, and Rust SDKs expose durable timer APIs, but
their service-mode workflow timer paths are not covered by this runner. Record
those paths as unexecuted until separate published-artifact evidence checks
timer completion, replay/restart, cancellation, and history for each relevant
workflow runtime. A passing embedded timer scenario does not fill those SDK
cells.

## Report a run

Add one comment to the active stable-release issue and update its fixed-tier
Expand Down
Loading