[ResponseOps] Rule execution fails due to null execution UUIDs#252618
Merged
doakalexi merged 2 commits intoelastic:mainfrom Feb 12, 2026
Merged
[ResponseOps] Rule execution fails due to null execution UUIDs#252618doakalexi merged 2 commits intoelastic:mainfrom
doakalexi merged 2 commits intoelastic:mainfrom
Conversation
Contributor
|
Pinging @elastic/response-ops (Team:ResponseOps) |
Contributor
💚 Build Succeeded
Metrics [docs]
History
|
Contributor
|
Starting backport for target branches: 9.2, 9.3 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 12, 2026
…ic#252618) Resolves elastic/response-ops-team#540 ## Summary Rule execution fails when the execution UUIDs is null. This PR filters out the null execution UUIDs from the query to prevent failures. ### Checklist - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### To verify 1. Create a rule that will create an active alert 2. Let it run a couple times 3. Verify that the rule is working as expected and nothing is broken 4. You can also let the alert recover and verify recovered alerts are working as expected (cherry picked from commit 0e423f1)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 12, 2026
…ic#252618) Resolves elastic/response-ops-team#540 ## Summary Rule execution fails when the execution UUIDs is null. This PR filters out the null execution UUIDs from the query to prevent failures. ### Checklist - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### To verify 1. Create a rule that will create an active alert 2. Let it run a couple times 3. Verify that the rule is working as expected and nothing is broken 4. You can also let the alert recover and verify recovered alerts are working as expected (cherry picked from commit 0e423f1)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Feb 12, 2026
…252618) (#252904) # Backport This will backport the following commits from `main` to `9.3`: - [[ResponseOps] Rule execution fails due to null execution UUIDs (#252618)](#252618) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexi Doak","email":"109488926+doakalexi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-02-12T15:19:21Z","message":"[ResponseOps] Rule execution fails due to null execution UUIDs (#252618)\n\nResolves https://github.com/elastic/response-ops-team/issues/540\n\n## Summary\n\nRule execution fails when the execution UUIDs is null. This PR filters\nout the null execution UUIDs from the query to prevent failures.\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n\n### To verify\n\n1. Create a rule that will create an active alert\n2. Let it run a couple times\n3. Verify that the rule is working as expected and nothing is broken\n4. You can also let the alert recover and verify recovered alerts are\nworking as expected","sha":"0e423f1a20d79cb11adefc1425c73b1467e93ac1","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","backport:version","v9.4.0","v9.3.1","v9.2.6"],"title":"[ResponseOps] Rule execution fails due to null execution UUIDs","number":252618,"url":"https://github.com/elastic/kibana/pull/252618","mergeCommit":{"message":"[ResponseOps] Rule execution fails due to null execution UUIDs (#252618)\n\nResolves https://github.com/elastic/response-ops-team/issues/540\n\n## Summary\n\nRule execution fails when the execution UUIDs is null. This PR filters\nout the null execution UUIDs from the query to prevent failures.\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n\n### To verify\n\n1. Create a rule that will create an active alert\n2. Let it run a couple times\n3. Verify that the rule is working as expected and nothing is broken\n4. You can also let the alert recover and verify recovered alerts are\nworking as expected","sha":"0e423f1a20d79cb11adefc1425c73b1467e93ac1"}},"sourceBranch":"main","suggestedTargetBranches":["9.3","9.2"],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/252618","number":252618,"mergeCommit":{"message":"[ResponseOps] Rule execution fails due to null execution UUIDs (#252618)\n\nResolves https://github.com/elastic/response-ops-team/issues/540\n\n## Summary\n\nRule execution fails when the execution UUIDs is null. This PR filters\nout the null execution UUIDs from the query to prevent failures.\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n\n### To verify\n\n1. Create a rule that will create an active alert\n2. Let it run a couple times\n3. Verify that the rule is working as expected and nothing is broken\n4. You can also let the alert recover and verify recovered alerts are\nworking as expected","sha":"0e423f1a20d79cb11adefc1425c73b1467e93ac1"}},{"branch":"9.3","label":"v9.3.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Alexi Doak <109488926+doakalexi@users.noreply.github.com>
kibanamachine
added a commit
that referenced
this pull request
Feb 12, 2026
…252618) (#252903) # Backport This will backport the following commits from `main` to `9.2`: - [[ResponseOps] Rule execution fails due to null execution UUIDs (#252618)](#252618) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexi Doak","email":"109488926+doakalexi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-02-12T15:19:21Z","message":"[ResponseOps] Rule execution fails due to null execution UUIDs (#252618)\n\nResolves https://github.com/elastic/response-ops-team/issues/540\n\n## Summary\n\nRule execution fails when the execution UUIDs is null. This PR filters\nout the null execution UUIDs from the query to prevent failures.\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n\n### To verify\n\n1. Create a rule that will create an active alert\n2. Let it run a couple times\n3. Verify that the rule is working as expected and nothing is broken\n4. You can also let the alert recover and verify recovered alerts are\nworking as expected","sha":"0e423f1a20d79cb11adefc1425c73b1467e93ac1","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","backport:version","v9.4.0","v9.3.1","v9.2.6"],"title":"[ResponseOps] Rule execution fails due to null execution UUIDs","number":252618,"url":"https://github.com/elastic/kibana/pull/252618","mergeCommit":{"message":"[ResponseOps] Rule execution fails due to null execution UUIDs (#252618)\n\nResolves https://github.com/elastic/response-ops-team/issues/540\n\n## Summary\n\nRule execution fails when the execution UUIDs is null. This PR filters\nout the null execution UUIDs from the query to prevent failures.\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n\n### To verify\n\n1. Create a rule that will create an active alert\n2. Let it run a couple times\n3. Verify that the rule is working as expected and nothing is broken\n4. You can also let the alert recover and verify recovered alerts are\nworking as expected","sha":"0e423f1a20d79cb11adefc1425c73b1467e93ac1"}},"sourceBranch":"main","suggestedTargetBranches":["9.3","9.2"],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/252618","number":252618,"mergeCommit":{"message":"[ResponseOps] Rule execution fails due to null execution UUIDs (#252618)\n\nResolves https://github.com/elastic/response-ops-team/issues/540\n\n## Summary\n\nRule execution fails when the execution UUIDs is null. This PR filters\nout the null execution UUIDs from the query to prevent failures.\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n\n### To verify\n\n1. Create a rule that will create an active alert\n2. Let it run a couple times\n3. Verify that the rule is working as expected and nothing is broken\n4. You can also let the alert recover and verify recovered alerts are\nworking as expected","sha":"0e423f1a20d79cb11adefc1425c73b1467e93ac1"}},{"branch":"9.3","label":"v9.3.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Alexi Doak <109488926+doakalexi@users.noreply.github.com>
mistic
pushed a commit
to mistic/kibana
that referenced
this pull request
Feb 13, 2026
…ic#252618) Resolves elastic/response-ops-team#540 ## Summary Rule execution fails when the execution UUIDs is null. This PR filters out the null execution UUIDs from the query to prevent failures. ### Checklist - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### To verify 1. Create a rule that will create an active alert 2. Let it run a couple times 3. Verify that the rule is working as expected and nothing is broken 4. You can also let the alert recover and verify recovered alerts are working as expected
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 https://github.com/elastic/response-ops-team/issues/540
Summary
Rule execution fails when the execution UUIDs is null. This PR filters out the null execution UUIDs from the query to prevent failures.
Checklist
To verify