temporalio / temporalio/features
Add BadScheduleActivityAttributes failure_reason to temporal_workflow_task_execution_failed metric
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Use case is when scheduling activity payload exceeds size limit and service fails workflow task with BadScheduleActivityAttributes and then terminates execution.
Contributor guide
No contributing guide indexed for this repository
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 locating the implementation and tests for the temporal_workflow_task_execution_failed metric and the BadScheduleActivityAttributes failure path. Reproduce or inspect the oversized activity payload case, then verify that the metric records failure_reason when the service fails the workflow task and terminates execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100