Multiple EEM consecutive policy of processing a single event

Question

Hi!
Please help me understand.
I do not quite understand the algorithm of MULTIPLE CONSECUTIVE policies are processed the SAME event.
As happens so that a policy ends and the other is called?
As ONE policy is activated understandable.  It ends with some "exit status" which affects the execution of "default action".
But as a start for the first second policy and what is the relationship between "exit status" and "entry status"?
This is the same and "exit status" stored in _entry_status system variable, after execution first policy,
and then verified by a second policy the of "entry status"?

Answer 1

Exactly Joseph!
I agree with you and checked.
But here is what is written in the documentation:
"sync (Mandatory)
A “yes” means that the policy (the event publish) will
run synchronously with the CLI command; a “no” means that the
event publish will be performed asynchronously with the CLI
command. The event detector will be notified when the policy
completes running. The exit status of the policy indicates whether
or not the CLI command should be executed: if the exit status is
zero, which means that the policy is executed successfully, the CLI
command will not be executed; otherwise, the CLI command will be
executed."
"Exit status" no effect in async mode, policies and cli command are executed independently.
It would be correct to replace the words synchronously and asynchronously,
replaced by an regardless and independly of the EEM policy.
Thanks!