How can the debug log for a playbook execution be viewed?

• A. On the Investigation page, select Debug Log from the playbook's action menu in the Recent Activity panel.
• B. Click Expand Scope in the debug window.
• C. In Administration > System Health > Playbook Run History, select the playbook execution entry, then select Log.
• D. Open the playbook in the Visual Playbook Editor, and select Debug Logs in Settings.

Answer: (C)

The debug log for a playbook execution can be viewed in the Playbook Run History found in the Administration section under System Health. This is the correct method because it provides a comprehensive view of the playbook executions, allowing users to select a specific execution entry to inspect its debug information. This log contains detailed information about the playbook's run, including any errors or issues that may have occurred, which is crucial for troubleshooting and optimizing playbook performance.

Accessing the debug log through this method ensures that users are looking at the execution history in a centralized location, where all relevant information about past runs is organized and easy to navigate. This approach allows for a historical perspective on the playbook's behavior over time, making it easier to identify patterns or recurring issues.

Other methods, such as selecting Debug Log from the action menu in the Recent Activity panel or using the Visual Playbook Editor, may not provide the same level of detail or might not be applicable in all contexts. Depending on the situation, those options could be limited in their ability to present a full picture of the playbook's operation during its execution.