temporalio / temporalio/temporal
Schedules - add option for execution workflowid to be "as-is" (not unique per run)
Open
Nobody has claimed this yet.
enhancement
schedules
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Schedules currently add timestamp of when the execution is started as part of workflowid.
This request is to add option for workflow id used to be as user defines in workflow options for each execution schedule creates.
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
Start by tracing how schedules construct workflow IDs and apply workflow options during each execution, then inspect the surrounding schedule behavior and tests. Done means an option allows scheduled executions to use the user-defined workflow ID as-is rather than adding a start timestamp, with coverage for the resulting ID behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100