[8.9] [DOCS] Add example of a rule with errored actions (#162368) (#162420)

# Backport

This will backport the following commits from `main` to `8.9`:
- [[DOCS] Add example of a rule with errored actions
(#162368)](https://github.com/elastic/kibana/pull/162368)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-07-24T16:00:06Z","message":"[DOCS]
Add example of a rule with errored actions
(#162368)","sha":"aa4fbc14a940ce66056000a4b0d7a6c78ce93004","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","docs","backport:prev-minor","v8.10.0"],"number":162368,"url":"https://github.com/elastic/kibana/pull/162368","mergeCommit":{"message":"[DOCS]
Add example of a rule with errored actions
(#162368)","sha":"aa4fbc14a940ce66056000a4b0d7a6c78ce93004"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/162368","number":162368,"mergeCommit":{"message":"[DOCS]
Add example of a rule with errored actions
(#162368)","sha":"aa4fbc14a940ce66056000a4b0d7a6c78ce93004"}}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>

docs/user/alerting/create-and-manage-rules.asciidoc

@@ -169,9 +169,8 @@ image::images/rules-imported-banner.png[Rules import banner,500]
 [[rule-details]]
 === View rule details
 
-You can determine the health of a rule by looking at the *Last response* column
-in  *{stack-manage-app}* > *{rules-ui}*. A rule can have one of the following
-responses:
+You can determine the health of a rule by looking at the *Last response* in *{stack-manage-app}* > *{rules-ui}*.
+A rule can have one of the following responses:
 
 `failed`:: The rule ran with errors.
 `succeeded`:: The rule ran without errors.
@@ -193,6 +192,14 @@ When an alert is created, it generates actions. If the conditions that caused th
 
 NOTE: The `flapping` state is possible only if you have enabled alert flapping detection in *{stack-manage-app}* > *{rules-ui}* > *Settings*. For each space, you can choose a look back window and threshold that are used to determine whether alerts are flapping. For example, you can specify that the alert must change status at least 6 times in the last 10 runs. If the rule has actions that run when the alert status changes, those actions are suppressed while the alert is flapping.
 
+If there are rule actions that failed to run successfully, you can see the details on the *History* tab.
+In the *Message* column, click the warning or expand icon image:images/expand-icon-2.png[double arrow icon to open a flyout with the document details] or click the number in the *Errored actions* column to open the *Errored Actions* panel.
+In this example, the action failed because the <<action-config-email-domain-allowlist,`xpack.actions.email.domain_allowlist`>> setting was updated and the action's email recipient is no longer included in the allowlist:
+
+[role="screenshot"]
+image::images/rule-details-errored-actions.png[Rule histor page with alerts that have errored actions]
+// NOTE: This is an autogenerated screenshot. Do not edit it directly.
+
 If an alert was affected by a maintenance window, its identifier appears in the *Maintenance windows* column.
 For more information about their impact on alert notifications, refer to <<maintenance-windows>>.