temporalio / temporalio/temporal
CreateSchedule with empty workflowID should not be allowed
Open
Nobody has claimed this yet.
potential-bug
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Expected Behavior
The call should fail
Actual Behavior
It is created with - Timestampe
This cause some of them to succeed, but others to fail with workflow ID conflict if you call it multiple times in 1s.
Steps to Reproduce the Problem
Specifications
- Version:
- Platform:
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 at the CreateSchedule API entry point and reproduce the call with an empty workflowID. Verify that the call fails rather than creating a timestamp-named schedule, and check repeated calls for the reported workflow ID conflict behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100