How a timestamp mismatch breaks telemetry replay — and the fix that solves it

A developer building a flight-instrument replay system discovered that React telemetry components rendered blank time-series charts despite receiving correct recorded data. The root cause was a timeline mismatch: charts anchored their x-axis to the current wall clock, so samples timestamped an hour in the past fell outside the visible window and were silently discarded. Single-value instruments were unaffected because they display the latest reading regardless of when it was recorded. The solution separates two timebases — recording time for the scrubber and wall-clock time for the components — and re-stamps each outgoing sample using an anchor offset calculated at the moment playback starts or resumes. This approach lets existing components consume replayed data without any modification to their internal logic.