The row ID of the lane's child record, for pinpointing which configuration to fix.
OptionalReasonWhy the lane was skipped. Absent when Status is Active.
The filter as rendered for this search, or null when the lane carries no filter.
OptionalRequiredMetadata keys this lane's RequiredMetadataKeys contract demands, if any.
Index name, entity name, or storage account ID — whatever identifies the lane to a human.
What happened to one retrieval lane.
Skippedis the interesting state and the reason this type exists. A lane is skipped when its restriction could not be applied safely — an unparseable filter, a template that lost a clause, a required metadata key the rendered filter never mentions. Skipping is the correct outcome (the alternative is querying unfiltered), but it is also silent: the search still succeeds, just against fewer sources. Without this record, "the filter broke and we searched three lanes instead of four" is indistinguishable from a scope that only ever had three.