[Experiment] Project schedule executions into visibility - #61
Draft
chaptersix wants to merge 1 commit into
Draft
Conversation
This was referenced Sep 5, 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
1 participant
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.
Describe and List now project real action kinds, types, execution identities, native statuses, and terminal times. Schedule visibility exposes ScheduleActionKind, ScheduleActionType, and ScheduleRunningExecutionCount while preserving existing physical mappings and keeping ScheduleRunningWorkflowCount at zero for activity schedules.
Started activities retain user search attributes and publish TemporalScheduledById and TemporalScheduledStartTime through the activity visibility provider. These reserved values are persisted separately from custom attributes. Shared context metadata uses activity-specific type and task-queue keys.
Validation: scheduler/activity tests, including scheduled metadata extraction, passed. Functional tests verify generic Describe/List results, kind/type queries, retry accounting, native activity termination, and scheduled metadata queries with preserved user search attributes.
This is an experimental draft stack; do not merge. The local integration base combines server main
ad7b2298dcce00688cfe3b83ab02819abf9249e8with the published readability stacke6c239bd4a368fcaaae7aefec85e3e4281f38045, preserving both sets of tests. Published branches are unchanged.Cross-repository dependencies:
40766d34ea6c0d2e59c100c1cf20cdf4fb286fe45fd10bc0a6cd7694373353cf6e00a0886a0b8167a6bed7c8ed3c4b90c467f003571c98b44ea8785bd80de5800cde0845596277a1af957c731eb1c0a2onexperiment/extensible-chasm-schedulerValidation uses Go 1.26.7 and an external four-module
go.workcontaining server, API-Go, SDK, and SDK/test. No dependency replacements or workspace files are committed; standalone CI needs these linked revisions wired explicitly until dependency versions are published.Complete server review order: contracts, activity, visibility, coverage.