X_JOB_ROW_STATUS_UNKNOWN
Means
a queue row carries a status this build does not know
Typical cause
a rolling deploy where a newer worker wrote a status this build has no name for. The decoders used to as-cast the column, which is worse than it sounds: steps.ts:263 returns a step's memoized output only when the status is completed, so a laundered value turned "this step already ran" into run it again
Fix
drain the older workers, or roll forward — x jobs show <id> --json prints the row. The reverse direction cannot fire: a release that only adds a status still knows every older one