---
title: "Comment by Arnold Holm on \"Validating market data before it reaches a WordPress dashboard\" | Hashnode"
description: "One REST-boundary test I would add: send the same XAUUSD/M1 bar twice with one changed OHLC value, then send an older bar after a newer batch. A 200 response an"
url: "https://hashnode.com/posts/validating-market-data-before-it-reaches-a-wordpress-dashboard/6a6c57e87b516a129fb33f77/comment/6ab41511e6071d9ed1e3b80b"
---

[Discussion](https://hashnode.com/posts/validating-market-data-before-it-reaches-a-wordpress-dashboard/6a6c57e87b516a129fb33f77)

Comment [Validating market data before it reaches a WordPress dashboard](https://hashnode.com/posts/validating-market-data-before-it-reaches-a-wordpress-dashboard/6a6c57e87b516a129fb33f77)

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Sep 23](https://hashnode.com/posts/validating-market-data-before-it-reaches-a-wordpress-dashboard/6a6c57e87b516a129fb33f77/comment/6ab41511e6071d9ed1e3b80b)

One REST-boundary test I would add: send the same XAUUSD/M1 bar twice with one changed OHLC value, then send an older bar after a newer batch. A 200 response and sorted timestamps are not enough here. The receiver needs an explicit rule: reject conflicting duplicates or record a versioned correction, and never advance the latest-valid watermark on a rejected batch. Store source time, ingestion time and last completed bar separately so a delayed VPS retry cannot make cached data look fresh.
