← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · ALERT HISTORIES

Crypto Alert Histories: Null vs Zero - Handle Missing Fields Correctly

An alert history lists when alerts fired and were delivered. A missing delivery time and a zero-alert day mean very different things.

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

Short answer

In an alert history, a trigger time with no delivery time may mean delivery failed or isn't logged; a day with zero alerts is only meaningful if the alert was active and the system was running that day. Before using alert history to judge a strategy or delivery reliability, separate 'didn't fire' from 'not active' and 'fired but not delivered'. Record delivery delay where possible.

Fields and what missing values mean

FieldNull / absent meansZero / empty means
Delivery timeFailed or not logged—
Alerts per dayAlert inactive: unknown0: active, no triggers
Condition valueNot stored—
ChannelNot recorded—
ExpiryNo expiry set—
Alert Histories: how to read each fieldAlert Histories: how to read each field: Delivery time — Failed or not logged; Alerts per day — Alert inactive: unknown; Condition value — Not stored; Channel — Not recorded; Expiry — No expiry set.Delivery timeFailed or not loggedAlerts per dayAlert inactive: unknownCondition valueNot storedChannelNot recordedExpiryNo expiry set
Alert Histories: missing vs zero, field by field. Original ChartsPod editorial graphic.

See Crypto Alert Histories on live data in the free ChartsPod terminal.

Open the ChartsPod terminal

Handling policy

Policy for this sourcePolicy for this source: Log active periods; Separate trigger and delivery; Store condition values; Measure delay; Note expiries.POLICY FOR THIS SOURCELog active periodsSeparate trigger and deliveryStore condition valuesMeasure delayNote expiries
Apply this policy to every alert histories request. Original ChartsPod editorial graphic.

Illustrative: an alert shows zero triggers in a week of volatile trading. It had expired on Monday; the zero reflected inactivity, not a quiet market.

Conclusion

Related: ChartsPod Telegram Alert Delivery: Settings to Check Before Your First Analysis, ChartsPod Price Alerts: Settings to Check Before Your First Analysis.

Record delivery delay where possible.

Test Crypto Alert Histories on a perpetual chart; no account is needed to chart.

Launch ChartsPod

Questions readers ask

Does zero alerts mean nothing happened?

Only if the alert was active.

What does a missing delivery time mean?

Failure or no logging; check.

What should I log?

Trigger, delivery, channel and condition value.

Sources and methodology

Field definitions come from DEX Screener's API reference, CoinGecko's onchain API documentation and Binance's Spot API documentation, read 17 October 2026. Where a schema was not visible in the documentation, this guide says so and describes defensive handling rather than asserting field behaviour.

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

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.