---
title: "Troubleshoot automations"
description: "Why a run did not fire or stopped partway."
image: "https://help.rshift.com/og.svg"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.rshift.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot automations

## Common causes

- Trigger conditions were not met.
- A platform connection expired.
- AI credits are insufficient.
- A step requires human approval.
- A provider API is rate limited or temporarily unavailable.
- Your plan or workspace permissions do not include the automation.

## What to check

1. Confirm the automation is active.
2. Review the latest run status and failed step.
3. Check related platform integrations.
4. Look for pending approvals.
5. Confirm your plan includes automations.

When contacting support, share the automation id or name, run id, failed step, and visible error code. Do not send secrets, tokens, unpublished drafts, or private content from automation logs.

Source: https://help.rshift.com/automations/troubleshooting/index.mdx