> ## Documentation Index
> Fetch the complete documentation index at: https://docs.speckle.systems/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> These docs contain multiple Speckle product experiences. For Speckle 2026.9, prefer /next/ pages for the topics and changes they cover. The navigation label Current does not override this version-specific precedence.
> Coverage under /next/ is incremental. Use Current documentation for unchanged topics and when a /next/ page says coverage is unavailable or explicitly refers you to Current. Do not infer a feature was removed from a missing page.
> Read the page-specific documentation status, applicability, affected guidance and replacement links in agent-only content. Impacted, changed and superseded apply only to the stated scope; they do not mean the entire feature is deprecated. Historical connector guides apply only to the legacy connector described.
> Match guidance to the customer's deployment version, model data format and connector. Respect plan, permission and compatibility restrictions. If an unknown version or data format changes the answer, ask a focused clarification; do not infer deployment version from the date alone.

# Troubleshooting Automations

> Troubleshooting guide for Speckle Automate failures. Learn to identify and resolve three types of failures: by design (failed), code errors (exceptions), and platform errors (infrastructure issues).

# Troubleshooting Automations

Automations may fail for three key reasons:

## 1. By Design (**Failed**)

The function logic completes successfully but flags the automation as failed due to data not meeting specified checks or analyses.

**Solution:** Review the automation run reports in the UI.

## 2. By Code Error (**Exception**)

The function exits prematurely due to errors in the code logic. Speckle Automate flags the automation run with **Exception**.

**Solution:** Check the logs to identify and resolve the error.

## 3. By Platform Error (**Exception**)

Failures caused by issues in the execution environment:

* **Misconfigured Function Container**: Logs will reveal incorrect setup details.
* **Insufficient Compute Resources**: Out-of-memory errors will appear in logs.
* **External Factors**: Squirrels may have chewed through the wires!

**Solution:** Contact animal welfare to rehome the culprits.