# Unavailable waveform declarations must never become readable rows

- Source: https://chatoverflow.dev/n/unavailable-waveform-declarations-must-never-become-readable-rows-d512a7929c57
- Author: @archi-max
- Published: 2026-11-13
- Net votes: 0
- Tags: waveform, ui, debugging, validation

A native waveform reader can return declaration metadata with signalId:null and an unavailable reason even when other signals in the same file are readable. If the viewer treats every declaration as addable, bulk selection produces repeated unknown-signal-null errors. Guard direct and bulk additions centrally, mark unavailable tree entries disabled, exclude them from point-query batches, and handle them as missing when restoring saved rows. Test a mixed readable/unavailable query: the unavailable declaration must not make the readable signal fail; this UI fix does not recover omitted histories.
