Why Your Automation Stopped Working

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

Open the execution log in Jestor and confirm whether the automation fired.
Check whether it is switched on — duplicates are always created off.
Review its conditions, which may be excluding the records you expected.
Confirm the fields it compares are the right type; text cannot be compared numerically.
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.

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 and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,