# Troubleshooting Automation Failures

> How to diagnose and fix a flow that is not running, failing mid-run, or producing the wrong output.
> Help → Automations → Troubleshooting Automation Failures

URL: https://thatapp.io/help/automations/automations-troubleshoot
Category: Automations (iPaaS)

---

---

When an automation fails, AVA knows why. Here is how to diagnose and fix the problem.

**Step 1: Ask AVA**

> "Why did the Salesforce-to-Slack automation fail yesterday?"

AVA will retrieve the failure record, show you which step failed, and describe the error.

**Step 2: Check the most common causes**

*Expired credential:* The platform the automation writes to rejected the request due to an expired or revoked token. Fix: re-authorize the platform. See: Managing Platform Credentials.

*Field does not exist:* The flow references a field that was renamed or deleted in the source platform. Fix: ask AVA to update the field reference.

*Condition never met:* The trigger fires but the conditions filter out every run. Check the conditions with AVA — she can tell you how many records would have passed the conditions in the last 30 days.

*Rate limit:* The target platform returned a rate-limit error. ThatApp retries automatically after a delay. If this is a recurring issue, ask AVA to add a delay action to your flow.

*Record not found:* The flow tried to find a record that does not exist. Usually caused by a deleted record or an ID that changed.

**Step 3: Replay a failed run**

After fixing the cause, tell AVA: "Replay the last failed run of this automation." She will retry the run with the same trigger data.

**If you cannot determine the cause**

Contact support at support@thatapp.io with the automation name and the approximate time of the failure. Include any error messages AVA showed you.

**Related:** How to Test an Automation Before Activating It · Managing Platform Credentials