temporalio / temporalio/temporal
Record activity started and failed event for activity in retry on workflow completion
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.
Currently, start and failure events for an activity that is constantly failing and in a retry loop are not recorded into the history until ScheduleToClose timeout is exhausted. If a workflow completes or continues as new before the status of the activity execution is essentially lost.
Describe the solution you'd like
Record started and failed events for all activities that are in a retry loop before completing the workflow.
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 activity retries are recorded in history and how workflow completion or Continue-As-New handles an activity that is still retrying. Confirm the behavior with a reproducing workflow, then verify that started and failed events are persisted before the workflow completes.
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
- 45/100