← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · ALERT HISTORIES TIMING

Crypto Alert Histories: Event Time vs Retrieval Time

An alert has a condition time, a trigger time, a send time and a receive time. Delays between them decide whether the alert was usable.

By ChartsPod Editorial Team · Reviewed by ChartsPod Research
Published · Updated · 5 min read

Short answer

For each alert, the condition became true at some moment (e.g. a bar close), the system detected and triggered it, sent it, and you received it. Logs often show only one of these. Record as many as available — especially condition time and receive time — to measure end-to-end delay. Alerts evaluated on bar close have an inherent delay of up to one bar after an intrabar move.

Which times the data carries

TimePresent?Meaning
Condition timeBar close or tickEvent
Trigger timeSystem logDetection
Send / receive timeChannelDelivery
Evaluation modeClose / intrabarInherent delay

Compare Crypto Alert Histories across Binance, Bybit, OKX and Hyperliquid markets.

Open markets in ChartsPod

What to record yourself

Field to storeWhy
condition timeEvent
triggered_atDetection
received_atDelivery
channelPath
evaluation modeContext
Alert Histories: a stored recordAlert Histories: a stored record: condition time — Event; triggered_at — Detection; received_at — Delivery; channel — Path; evaluation mode — Context.condition timeEventtriggered_atDetectionreceived_atDeliverychannelPathevaluation modeContext
Every alert histories row carries its own clock. Original ChartsPod editorial graphic.

Example

Alert Histories: event vs retrieval (illustrative)Alert Histories: event vs retrieval (illustrative): 14:00:00: Bar closes: condition true; 14:00:02: Triggered; 14:00:03: Sent; 14:00:41: Received (channel delay).14:00:00Bar closes: condition true14:00:02Triggered14:00:03Sent14:00:41Received (channel delay)
Two clocks, one record. Original ChartsPod editorial graphic.

Illustrative: a messaging channel delivered alerts 38 seconds after trigger during a busy period; in-app notices arrived in two seconds. Without both times, the delay was invisible.

Related: Crypto Alert Histories: Null vs Zero - Handle Missing Fields Correctly, ChartsPod Telegram Alert Delivery: Settings to Check Before Your First Analysis.

Alerts evaluated on bar close have an inherent delay of up to one bar after an intrabar move.

Check Crypto Alert Histories against a live market before relying on it.

Try it in ChartsPod

Questions readers ask

What times does an alert have?

Condition, trigger, send and receive.

How do I measure delay?

Receive minus condition time.

Do bar-close alerts lag?

Up to one bar after intrabar moves.

Sources and methodology

Field definitions come from DEX Screener's API reference and CoinGecko's onchain API documentation, read 17 October 2026. Where a schema doesn't document a timestamp, this guide says so and recommends recording retrieval time yourself.

  1. ChartsPod documentation — guides for order flow, derivatives, alerts, backtests, journal and workspaces.
  2. ChartsPod: product overview, pricing and FAQ — free terminal, venues, modules, no order placement; checked 17 Oct 2026.

This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.

CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.