Issues with alert statuses UI

[mikecote]

I've noticed two strange behaviours around alert statuses that I thought would be worth discussing.

1. When the alert is disabled, it still displays the status from the last execution. I found this strange when it was "error" as the last execution status since it would never go away until the alert is re-enabled. There is also no clear indication in the alert list if the alert is disabled (to be solved in Visual indication for disabled or muted alerts #80310).
2. When the alert is enabled, it takes some time for the status to be updated. In the meantime, it still contains the previous execution status (ex: error that was set before disabling the alert). Should this change to "pending" like when the alert is created?

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[pmuellr]

1. I think the UI should take into account the enabled state of the alert - we do want the execution status to be sticky, I think, for diagnostic purposes. So I think the fix would be to change the UI to display "disabled" for alerts that are disabled, rather than display the stored status.

2. Makes sense to me to clear the execution status back to pending (and clear the other fields like error message, etc) when an alert transitions from disabled to enabled.