An Alert Management Rule doesn't show in the list of Alert Executions related list of the Alert form, if the Automatic executions limit on the workflow attached to that rule is less than the number of executions of that specific alert.

Symptom:
Let us assume an Environment where the customer has 3 Alert Management Rules, called A, B and C.
For an alert, let us assume that the customer wants to process the above alert rules in the following order: A, B and then C. However, due to a logic flow in the Alert Filters, the process will run in the following order: A, B and then A again.
Assume that Rule A has the Automatic executions limit on the workflow attached to that rule set to 1, which is the default value. On the Alert > Alert Executions, we will only see Alert A and B, which gives the impression that Alert C was never executed because the alert did not match the Alert Filter. Instead, the Alert Executions should show the following execution order: Alert A, Alert B and then Alert A again, which would show a flow in the logic.

1. Set up 2 Alert Management Rules - called Alert A and Alert B - which should always be in a loop. For example, when Alert A sees that the alert is out of maintenance mode, it puts the alert in maintenance mode. When Alert B sees that the alert is in maintenance, it will remove it from maintenance mode. This is all done via workflows which are defined in Alert Management Rule > Actions.
2. In the Alert Management Rule > Actions, make sure that the Automatic executions limit is set to 1 - which is the default value.

Expected behavior:
In the Alert > Alert Executions, under the related lists, the execution procedure should show the following order: Rule A, Rule B and Rule A. It should then stop because the limit set on the execution of the workflow would prevent the Alert from being put back to Maintenance Mode.

Actual behavior:
In the Alert > Alert Executions, under the related lists, the execution procedure shows the following order: Rule A and Rule B. Despite the fact that Rule A was triggered a second time, it is not showing because the workflow had a limit set to 1. However, logically, Rule A was still executed and it should show.