> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/resilience-testing/chaos-testing/experiments.md).

# Chaos Experiments

Advanced chaos experiments with dynamic content selection

{% @harness-package-selector/package-selector platforms="%5B%7B%22label%22%3A%22Chaos%20Studio%22%2C%22slug%22%3A%22chaos-studio%22%2C%22path%22%3A%22resilience-testing%2Fchaos-testing%2Fexperiments%2Fchaos-studio-experiments%22%7D%2C%7B%22label%22%3A%22Legacy%20Chaos%20Studio%20(deprecated)%22%2C%22slug%22%3A%22legacy-chaos-studio-deprecated%22%2C%22path%22%3A%22resilience-testing%2Fchaos-testing%2Fexperiments%2Flegacy-chaos-studio-deprecated-experiments%22%7D%5D" %}

## Troubleshooting <a href="#troubleshooting" id="troubleshooting"></a>

<details>

<summary>An experiment moves to the QUEUED state when I run it</summary>

Check whether the cluster has sufficient resources available, then check the logs of the control plane components, such as Chaos Manager and Kubernetes IFS. Go to [Troubleshooting](https://developer.harness.io/resilience-testing/troubleshooting-and-resources/troubleshooting.md#executing-an-experiment-moves-it-to-queued-state) to review the full checklist.

</details>

<details>

<summary>An experiment moves directly to the ERROR state with no execution data</summary>

The experiment reached the subscriber, but the subscriber failed to start it. Check the workflow controller logs, and if they report that the experiment run name exceeds the limit, shorten the experiment name. Go to [Troubleshooting](https://developer.harness.io/resilience-testing/troubleshooting-and-resources/troubleshooting.md#experiment-directly-moves-to-error-state-with-no-execution-data) to review the debug steps.

</details>

## Next steps <a href="#next-steps" id="next-steps"></a>

* [Learn about Probes](https://developer.harness.io/resilience-testing/chaos-testing/probes.md) - Validate system health and behavior during experiments
* [Explore Actions](https://developer.harness.io/resilience-testing/chaos-testing/actions.md) - Execute custom operations, delays, and scripts during experiments
* [Browse Chaos Faults](https://developer.harness.io/resilience-testing/chaos-engineering/faults/chaos-fault-categories/chaos-faults-reference.md) - Discover available fault types for your experiments

{% @harness-feedback/feedback %}
