[Security Solution] Empty execution results is showing when rule is created with non existing index

[ghost]

Related to: #136138, #137935

Describe the bug:
Empty execution results is showing under execution results when rule is created with non existing index and warnings are coming.

Build Details:

VERSION: 8.5.0 snapshot
BUILD: 55925
COMMIT: dc43193d73c5869335a239c7012528bb1fffd509

Pre-conditions:

1. Elasticsearch should be up and running
2. Kibana should be up and running

Steps to Reproduce:

1. Navigate to Security-->Manage-->Rules.
2. Click on create rule.
3. Select custom query rule.
4. Enter any index pattern which is not created.
5. Enter all the other fields and create the rule.
6. Check the Execution results.

Expected Result
Empty values should not be present under execution results.

Actual Result
Empty values are present under execution results.

Screenshots:

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[banderror]

Could be caused by the same reasons as this one: #136138

[banderror]

@karanverma-qasource If you have any other details to share about your setup and steps, that could help. I wasn't able to reproduce it using the Steps to Reproduce from the description. It showed only warnings as expected:

[ghost]

Hi @banderror,

I have used small runtime like 10 seconds with non existing index, and Empty string entry came, can you please check this with small runtime. Please let us know if are missing something.

Thanks!

[banderror]

@karanverma-qasource Thank you, that is helpful. With the same rule parameters as yours and running this on a local laptop I see this:

• It always shows the Warning status. I don't see any empty statuses in the table.
• The (Empty string) timestamp appears from time to time. Sometimes when I refresh the table it appears and sometimes it gets hidden (or maybe replaced by a non-empty timestamp value).

I think this could be enough information for now. Thank you @karanverma-qasource!