temporalio / temporalio/temporal
Pin a particular workflow run to prevent it from getting purged
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Problem Description
Coming from the fact there are some unusual/rare events that happen in a run (like some race condition, for example, which are difficult to reproduce) that needs to be looked into at a later point in time. And the devs have to race against time to solve the issue before the run gets purged.
Describe the solution you'd like
Temporal can provide a button to mark/pin/save a run and this makes sure the run would not get purged. Later, this workflow run can be referenced with a link or otherwise. This run stored in the DB should not get deleted unless explicitly deleted.
Alternatives considered
Downloading workflow history json probably would work as a stopgap for saving it locally. But, some better way from the Temporal UI would be really helpful such that others can also look at it.
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. Begin by clarifying how the Temporal UI should mark a workflow run and how retention and purge behavior should treat it; done means a pinned run remains referenceable and is not purged until explicitly deleted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100