[Response Ops] Fixing issue with empty row in execution log table when rule is running #129151
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.
Resolves #129126
Summary
Updates the exec log aggregation to exclude
execute-start
events. This prevents an empty row from being returned for currently running rule executions.To Verify
See description in #129126 to reproduce the issue. With this branch, you should no longer see an empty row returned while a rule is mid-execution.
Checklist