temporalio / temporalio/temporal
Add TemporalScheduledStartTime and TemporalScheduledById to the StartWorkflow Event message
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
A user would like to validate the originating starter for WFs started by a schedule. Using Search Attributes is problematic. The ideal solution is to add a similar field for cron, cron_schedule, for Schedules.
Describe the solution you'd like
We would like to add TemporalScheduledStartTime and TemporalScheduledById to the start event message as opposed to just search attributes.
Describe alternatives you've considered
The user tried using Search Attributes but found them problematic for 2 reasons:
- it's feasible that the schedule Search Attributes could be spoofed
- the WFID in the Schedule Search Attributes includes a timestamp which breaks client logic
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the StartWorkflow event message and the schedule-start path, then trace how scheduled-workflow metadata reaches that event; done means the event exposes TemporalScheduledStartTime and TemporalScheduledById instead of relying only on search attributes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100