How to Check Whether an Automation Actually Ran

The automation execution log records what fired and when. Without it, a process that stops working silently is indistinguishable from one that was never configured.

Why silent failures are the worst kind

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
Changes appearing with no obvious cause

Where to look when something seems wrong

The execution log, showing whether the automation ran
The table history view, filtered by source to separate automation changes from user edits
The updates tab on the record, showing changes in chat format
The automation's on/off state, particularly after a duplication
Conditions on the automation, which may be excluding records unexpectedly

How to investigate in Jestor

Open the automation execution log in Jestor to confirm whether it fired.
If it did not, check whether the automation is switched on — duplicates arrive off.
Open the table history view and filter by source to see automation-driven changes.
Filter by date to narrow to the period in question.
Export the filtered history if the investigation needs to go outside the platform.

Why choose Jestor for traceable automation?

Jestor records the source of every change — a user, an automation, or the API — so a record that changed unexpectedly can be traced to what changed it rather than to who is blamed for it.

Combined with the execution log, that gives both sides of the question: whether the automation ran, and what it did when it did.

Frequently Asked Questions

Where is the execution log?

Inside the platform, alongside the automations. See jestor.com.

Can I tell a user edit from an automation change?

Yes, by filtering the table history by source.

Why might an automation not be running?

It may be switched off, or its conditions may exclude the records.

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,