> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Why Your Automation Stopped Working
- URL: https://blog.jestor.com/why-automation-stopped-working/
- Published: 2026-09-17T22:32:03.000Z
- Updated: 2026-09-17T22:32:03.000Z
- Author: Bruno Bannach

Diagnosing **why an automation stopped working** starts with a question most people skip: did it ever run, or did it stop? The execution log answers that before any other investigation is worth starting.

## Why silent failures are the dangerous ones

An automation that fails loudly gets fixed. One that fails quietly corrupts a process for weeks.

- Messages nobody received and nobody missed
- Records not updated, discovered during an audit
- Two automations conflicting with no visible symptom
- A duplicate created and never switched on

## A diagnostic order

| Check             | What it rules out                                     |
| ----------------- | ----------------------------------------------------- |
| **Execution log** | Whether it fired at all                               |
| **Switch state**  | A duplicate that was never enabled                    |
| **Conditions**    | Records being excluded unexpectedly                   |
| **Field types**   | Comparisons failing because a value is stored as text |
| **Table history** | Whether something else changed the record first       |

## How to investigate in Jestor

1. Open the execution log in **Jestor** and confirm whether the automation fired.
2. Check whether it is switched on — duplicates are always created off.
3. Review its conditions, which may be excluding the records you expected.
4. Confirm the fields it compares are the right type; text cannot be compared numerically.
5. Filter the table history by source and date to see whether another automation acted first.

## Why choose Jestor for reliable automation?

**Jestor** records the source of every change — user, automation, or **API** — which means an unexpected result can be traced to what caused it rather than debated.

Duplicates arriving switched off is a deliberate safeguard, and also the single most common explanation when a newly copied automation appears to do nothing.

## Frequently Asked Questions

### Where do I see whether it ran?

In the automation execution log. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Why would a duplicate not run?

Duplicates are always created switched off.

### Can I tell which automation changed a record?

Yes, by filtering the table history by source.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.