# Why did a trigger not fire?

> An automation did not run, ran for the wrong sequence, or stopped altogether: scope, conditions, and what happens to a trigger after repeated failures.

**A trigger listens for one event across everything it is scoped to, so the usual problems are that it is scoped wider or narrower than you assumed, or a condition excluded the contact. A trigger that keeps failing is also switched off after repeated failures rather than retrying forever.**

_Status: Reviewed – written against Reply's product documentation on 2026-09-21, not yet confirmed against the running product._

## Quick fix

1. Confirm the trigger is still enabled. A trigger whose action keeps failing is switched off.
2. Check its scope. Unless you added a condition naming a sequence, it fires for **every** sequence, not just the one you built it for.
3. Check its conditions against one contact that should have fired it; a condition that excludes the contact looks exactly like a trigger that did not run.
4. Confirm the event you expect is the event the trigger listens for. "Replied" and "positive reply" are different events.
5. Reproduce it with one contact and watch whether it fires.

Didn't work? [Contact Reply support](https://support.reply.io/); the team can check your account directly.

## Symptom

Something that should happen automatically did not; a contact was not created in your CRM, an activity was not logged, a contact was not moved. Or the opposite: it ran for contacts in a sequence it was never meant to touch.

## Most likely causes

| Cause | How to recognize it |
| --- | --- |
| **The trigger is scoped wider than you assumed** | It fires for contacts in sequences you did not intend. Triggers are not tied to one sequence unless you say so |
| A condition excluded the contact | It fires for some contacts and not others, and the ones that fail have something in common |
| The event is not the one you think | Nothing fires at all, even though the thing you expected clearly happened |
| The trigger was switched off after repeated failures | It used to work and stopped. Nothing changed on your side |
| The action's destination rejected it | The trigger fired, the action failed – usually a permission or a required field at the other end |
| The contact's own state stopped it | Opted-out, deleted or finished contacts do not produce every event |

## Diagnostic checklist

1. **Check enabled first.** Repeated failures switch a trigger off, and this is the explanation for most "it used to work" cases.
2. **Read the scope as written, not as intended.** If no condition names a sequence, it applies to all of them. This is the most common surprise, in both directions.
3. **Take one contact that should have fired it** and walk its conditions one at a time. This is faster than reasoning about the rule.
4. **Check the event name.** Reply distinguishes events that sound similar: a reply, a categorized reply, a positive reply and a link click are four different things.
5. **Check the other end.** If the trigger writes somewhere else, the failure may be there: a missing required field or a permission, not the trigger itself.

## Resolution

### It fires for the wrong sequences

Add a condition that names the sequence you want. Without one, the trigger is account-wide. This is the fix for both "it ran where it should not" and "it ran too often".

### A condition excluded the contact

Loosen or correct the condition. Check the field's value on a real contact rather than assuming; an empty field fails most comparisons, and a text comparison fails on case and spacing.

### The wrong event

Change the trigger to the event that actually occurs. If you want to react to a positive reply specifically, use that event rather than a general reply plus a filter.

### It was switched off

Fix the underlying failure first, then re-enable it. Re-enabling without fixing the action means it will be switched off again.

### The action fails at its destination

Check whatever the trigger writes to: is the connection still authorized, does the required field exist, does the account have permission to create that record? The trigger firing and the action succeeding are two separate things.

## Verification

Reproduce the event with one contact and confirm both halves: the trigger fired, and the action completed where it was supposed to. Then check it again a day later; a trigger that fails intermittently is switched off gradually, not at once.

## Prevention

- Scope every trigger to a sequence explicitly, even when you only have one. You will add a second sequence later.
- Check triggers after changing anything at the destination: a renamed field silently breaks the action.
- Prefer the specific event over a general event plus conditions.
- Review your enabled triggers periodically; the ones that switched themselves off do not announce it.

## FAQ

### Does a trigger apply only to the sequence I created it in?

No. Unless a condition names a sequence, it applies to every sequence in the account.

### Why did my trigger stop working on its own?

Repeated action failures switch it off rather than letting it retry indefinitely. Fix the action, then re-enable.

### Can two triggers react to the same event?

Yes, and both run. If you see an action happening twice, look for a second trigger on the same event.

## Still stuck? Contact Reply support

If these steps didn't solve the problem, the Reply support team can look at your
account directly. Open the [Reply Help Center](https://support.reply.io/) and send
the team a message.

To get an answer faster, include:

- the trigger's event, conditions and action
- whether it is still enabled
- one contact that should have fired it, and when
- where the action was supposed to write, and your timezone

Don't send passwords, API keys, or access tokens.

## Related

- [Why did a condition send contacts the wrong way?](/troubleshooting/condition-sent-contacts-the-wrong-way/) – the same field-comparison traps
- [Why was a webhook not received?](/troubleshooting/webhook-was-not-received/) – the same shape of problem over HTTP
- [Why was a contact not enrolled?](/troubleshooting/contact-was-not-enrolled/)

## Build with Reply

- Webhooks: [Webhook events](https://docs.reply.io/api-reference/introduction) – the event catalogue
- MCP: [docs.reply.io/mcp](https://docs.reply.io/mcp/overview) – review automations from an assistant