Services and resources

Free incident-preparation guide

TradingView Webhook Mismatch Evidence Checklist

The timestamps, alert settings, payloads and downstream logs needed to find where a TradingView signal and an automated trade first diverged.

The checklist

  1. 1

    Choose one incident

    Use one missing, late, duplicated or unexpected trade instead of mixing several unrelated failures.

  2. 2

    Freeze the time basis

    Record chart timezone, exchange timezone, receiver timezone and the exact timestamp format used by every log.

  3. 3

    Capture the chart state

    Record symbol, timeframe, bar open and close times, relevant inputs and whether the signal used a forming or confirmed bar.

  4. 4

    Preserve the Pine source

    Provide the authorized editable version that was running when the incident occurred, including imported-library versions.

  5. 5

    Export alert settings

    Capture the alert condition, frequency, expiration, message template and whether the alert was created before or after a script change.

  6. 6

    Redact the payload

    Keep field names and non-secret values, but remove webhook URLs, tokens, API keys, account IDs and credentials.

  7. 7

    Collect receiver evidence

    Preserve request timestamp, HTTP status, parsed fields, validation result and queue or retry events around the incident.

  8. 8

    Collect execution evidence

    Include the broker or exchange request, response code, fill data and nearby error lines for the same time window.

  9. 9

    State the expected result

    Write the exact order, side, quantity, price rule and timing that should have followed from the signal.

  10. 10

    Define completion

    Agree whether the diagnostic ends at a proven divergence point, a reproducible case or a separately quoted repair.

Common questions

Do you need access to my broker or exchange account?

No. A safe diagnostic uses redacted source, configuration and logs. Credentials, API secrets and remote account access are not requested.

Does a chart marker prove that a webhook was sent?

No. The chart calculation, alert engine, HTTP delivery, receiver parsing and broker execution are separate stages and require separate evidence.

Can historical chart behavior reproduce a realtime alert exactly?

Not always. Intrabar values, higher-timeframe requests, alert snapshots and data-feed differences can make realtime and reloaded history differ. The timing model must be documented first.

Free diagnostic resource

Open the free Pine MTF timing inspector

Compare developing and confirmed higher-timeframe values before treating a visual chart match as alert evidence.

Open the free tool

Ready for a feasibility check?

Pine/Webhook Reconciliation — 39 EUR

Review the service