---
title: Automations Troubleshooting
description: Fix Capawesome Cloud automations that aren't triggering — webhook registration, pattern mismatches, skip keywords, and build minutes.
---

# Troubleshooting

## My automation isn't triggering a build

Check these causes, roughly in order of likelihood:

1. **Pattern mismatch** — the pushed branch or tag doesn't match the automation's [trigger pattern](reference.md#trigger-pattern-syntax). Confirm the pattern (e.g. `v*` matches tags, not branches).
2. **Skip keyword** — the head commit message contains a [skip keyword](filter-by-commit-message.md#skip-keywords) like `[skip ci]`.
3. **Disabled** — the automation is toggled off. Check the [Automations](https://console.cloud.capawesome.io/apps/_/automations){:target="_blank"} page.
4. **Webhook not registered** — if automatic webhook registration failed (insufficient permissions or a self-hosted provider), the Git event never reaches Capawesome Cloud. Configure it manually — see [Set up the Git webhook](webhooks.md).
5. **No build minutes** — your plan's [build minutes](../native-builds/limits.md) are exhausted.

## How do I confirm the webhook is working?

Push a commit or create a tag that matches the trigger pattern, then check that the automation's **Last triggered** timestamp updates and a new build appears on the [Builds](https://console.cloud.capawesome.io/apps/_/builds){:target="_blank"} page. See [Set up the Git webhook](webhooks.md#verifying-the-webhook).

## A build was triggered but failed

That's a build problem, not an automation problem — see [Native Builds troubleshooting](../native-builds/troubleshooting.md).