You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(diagnostics): diagnose large workflow histories (#8490)
## What changed?
The diagnostics failure invariant now recognizes workflows that failed
with the "history exceeds limit" error and reports a dedicated root
cause, including the history event count of the failed workflow.
Misc:
- The variable `FailureReasonSizeExceedsLimit` has been renamed to
`FailureReasonHistorySizeExceedsLimit`
## Why?
When a workflow fails because its history grew past the size or event
count limit, diagnostics previously bucketed it as a generic custom
error ("Customised error returned by the activity/workflow"), which
points users in the wrong direction. The new root cause names the actual
problem. The runbook update linked below suggests remediation
(ContinueAsNew, smaller payloads, avoiding unbounded loops in one run).
## How did you test it?
```
make pr GEN_DIR=service/worker/diagnostics # clean, no generated diffs
make build
make test # all unit tests pass
go test -race ./service/worker/diagnostics/...
```
## Potential risks
None — isolated change to the diagnostics worker; no API/schema/flag
impact.
## Release notes
Workflow diagnostics now identifies failures caused by exceeding history
size/count limits and surfaces an actionable root cause.
## Documentation Changes
Failures runbook update:
cadence-workflow/Cadence-Docs#406
---------
Signed-off-by: Adhitya Mamallan <adhitya.mamallan@uber.com>
0 commit comments