> ## 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.

# How to Troubleshoot a Failing Integration
- URL: https://blog.jestor.com/troubleshoot-a-failing-integration/
- Published: 2026-09-17T22:36:26.000Z
- Updated: 2026-09-17T22:36:26.000Z
- Author: Bruno Bannach

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

1. Open the execution log in **Jestor** and confirm whether the automation fired.
2. Check that it is switched on — duplicates are always created off.
3. Review conditions, which may be excluding the records you expected.
4. Confirm the fields compared are the right type; text cannot be compared numerically.
5. 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](https://jestor.com/?ref=blog.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](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.