[Wf-Diagnostics] Timeout invariant to identify and collect all timeouts in a workflow execution #6220
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
Introducing an invariant interface that can check and collect issues in a workflow. timeout is one invariant that identifies timeouts within a workflow execution history.
The execution history input is kept out of the interface definition since not all invariants will rely on the workflow execution data.
Each invariant will need different data input based on what issues they identify.
This usage of this interface will be a workflow within the worker service
Why?
This invariant will be used within the workflow diagnostics to run checks to identify timeouts in workflow execution
How did you test it?
unit tests
Potential risks
Release notes
Documentation Changes