GuidePlatformv1
Troubleshooting
Diagnosing why an automation failed and applying a fix — via the plugin, which searches execution history and proposes remediation.
Ask Claude to diagnose a failing automation — Claude searches execution history, identifies the failure, and proposes a fix. See Diagnosing failed runs for the full plugin walkthrough.
Point it at the failing automation or a specific execution; it diagnoses the root cause and offers a concrete remediation path.
Examples
- "Why did order #123 not process?"
- "What's broken for Acme Corp?"
- "Why is Acme's Mindbody sync behind?"
- "Check on customer support+acme@example.com — anything failing today?"
UI fallback
The Automation Editor's Troubleshooting section (under Platform UI) covers how to inspect execution history, copy step numbers, and debug from graphical history manually.
Related docs
Last updated May 4, 2026