How to Troubleshoot a Failing Integration

To troubleshoot a failing integration, establish first whether anything ran at all. That single question eliminates most of the possible causes before any investigation begins.

Why integration failures are hard to diagnose

The failure is usually silent and the symptom appears elsewhere.

Records not updated, discovered days later
Two systems disagreeing with no obvious cause
A change made by an integration and attributed to a person
An automation switched off and assumed to be running

A diagnostic order

Step	What it rules out
Execution log	Whether the trigger fired
Switch state	A duplicate created switched off
Conditions	Records excluded unexpectedly
Field types	Comparisons failing on text values
Change source	Whether something else acted first

How to investigate in Jestor

Open the execution log in Jestor and confirm whether the automation fired.
Check that it is switched on — duplicates are always created off.
Review conditions, which may be excluding the records you expected.
Confirm the fields compared are the right type; text cannot be compared numerically.
Filter the table history by source and date to see whether a user, an automation, or the API acted.

Why choose Jestor for diagnosable integrations?

Jestor records the source of every change, which means an unexpected value can be attributed to what caused it rather than debated between teams.

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

What should I check first?

The execution log, to confirm whether it ran. See jestor.com.

Why would a duplicate not run?

Duplicates are created switched off.

Can I tell what changed a record?

Yes, by filtering the 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,