Differentiate skipped and fired for timer command results
Open
Nobody has claimed this yet.
feature
medium
- Dominant language
- Go
- Stars
- 661
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
This could be useful to manual skip the timer to wake up a workflow and then go back to the timer again if this skipped
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
No files, tests, or entry points are named. Start by locating timer command result handling and the workflow behavior for manually skipped timers, then clarify how skipped and fired states should differ when returning to the timer. Done should include an agreed state distinction and coverage for the skip-then-resume scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100