Repository navigation
Conversation
Bump durabletask-go to 98658f3 in the root and examples modules, which brings the workflow schedule client (dapr/dapr#11095). client.NewWorkflowClient returns that client, so the schedule API needs no wrapper here. Add examples/workflow-schedule: create a schedule with repeats, wait for it to complete, list its runs by instance ID prefix, trigger a second schedule, then delete both and purge the runs. Validate it in a new validate-example-dapr-master job, which runs against a daprd built from dapr master, because no release has workflow schedules yet. The release jobs are unchanged. Signed-off-by: joshvanl <me@joshvanl.dev>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #864 +/- ##
=======================================
Coverage 57.38% 57.38%
=======================================
Files 53 53
Lines 3888 3888
=======================================
Hits 2231 2231
Misses 1503 1503
Partials 154 154 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
🟡 Changes recommended
Incomplete pagination can omit runs and schedules or cause a nil-pointer panic, while rerun cleanup leaves previously triggered manual runs unpurged.
3 open issues
What changed in this PR
Adds a workflow scheduling example using the schedule APIs exposed directly by client.NewWorkflowClient(), with validation against Dapr master until a supporting runtime release is available.
Changes:
- Updates durabletask-go to commit
98658f3in the root and examples modules. - Adds an example covering repeated runs, manual triggering, schedule inspection, deletion, and run cleanup.
- Adds a master-runtime validation job while leaving release validation jobs unchanged.
| File | Description |
|---|---|
go.sum |
Updates durabletask-go checksums. |
go.mod |
Upgrades the SDK’s durabletask-go dependency. |
examples/workflow-schedule/README.md |
Documents prerequisites, execution, expected output, and schedule behavior. |
examples/workflow-schedule/main.go |
Demonstrates workflow scheduling and cleanup APIs. |
examples/workflow-schedule/config/redis.yaml |
Configures Redis as the workflow actor state store. |
examples/go.sum |
Updates the examples’ dependency checksums. |
examples/go.mod |
Aligns examples with the upgraded durabletask-go dependency. |
.github/workflows/validate_examples.yaml |
Adds schedule-example validation against a source-built Dapr runtime. |
Review effort: Balanced
Signed-off-by: joshvanl <me@joshvanl.dev>
javier-aliaga
approved these changes
Nov 16, 2026
cicoyle
approved these changes
Nov 16, 2026
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.

Bump durabletask-go to 98658f3 in the root and examples modules, which brings the workflow schedule client (dapr/dapr#11095). client.NewWorkflowClient returns that client, so the schedule API needs no wrapper here.
Add examples/workflow-schedule: create a schedule with repeats, wait for it to complete, list its runs by instance ID prefix, trigger a second schedule, then delete both and purge the runs.
Validate it in a new validate-example-dapr-master job, which runs against a daprd built from dapr master, because no release has workflow schedules yet. The release jobs are unchanged.