Skip to content

Troubleshooting

Every playbook execution in CYBERQUEST is fully logged. The system records all variables and input parameters used in each action, providing a complete view of the execution flow.

By reviewing the values recorded for each step or action, it is possible to debug and inspect the playbook, identify issues, and ensure that the mitigation workflow behaves as expected.

How to Use Execution Logs

1.Navigate to the Execution History section: Execution History

2.Select the playbook run to review.

3.Inspect each action to see:

  • Input parameters
  • Output results
  • Any errors or warnings

Common Troubleshooting Scenarios

  • Action fails to execute:
  • Check the input parameters for missing or invalid values.
  • Ensure any required external integrations (APIs, DTS objects) are correctly configured.
  • Unexpected output:
  • Review the input values for each step in the execution history.
  • Verify logic in conditional actions (e.g., IF statements, custom scripts).
  • Playbook stops mid-execution:
  • Confirm that array-based actions like Count receive valid arrays.
  • Check for script errors in custom DTS objects.
  • External API actions fail:
  • Verify API credentials and endpoint availability.
  • Ensure network access is allowed from the CYBERQUEST server to the external service.