Playbooks store a full run-history that records every trigger evaluation and the resulting action status. Nutanix documentation recommends examining this History tab first when a playbook does not appear to run—it confirms whether the trigger fired, if conditions were met, and why an action may have been skipped or failed. Therefore, validating the configuration is best started by reviewing the playbook’s execution history rather than changing project context, quotas, or rebooting Prism Central.

A. Execution context need not be moved to Prism Element; power-off VM actions execute perfectly from Prism Central, so changing context will not validate trigger issues.

B. Prism Central changes are applied immediately; rebooting is unnecessary and gives no diagnostic insight into why a playbook failed to run.

C. Resource quotas affect VM provisioning, not whether an automation playbook trigger fires; increasing CPU/memory limits will not influence playbook execution.

1. Nutanix Prism Central Administration Guide 6.10, “Automation – Viewing Playbook Execution History,” pp. 127-129: explains using the History tab to verify trigger evaluations.

2. Nutanix University, NCP-MCA v6.10 Courseware Module “Playbooks & X-Play,” Section “Troubleshooting Playbooks,” slide 14: instructs to check Execution History first when playbooks do not run.

3. Nutanix Official Documentation Portal, KB-7525 “Playbooks – Troubleshooting Basics,” Step 1: “Inspect the History tab to confirm the trigger fired and review error details.”