See if that key appears in more than one of the utt2spk files in the
split data directory that you are using (e.g.
data/test/split10/*/utt2spk). I imagine it does. If it does, then
it's likely because at some point you (or someone) ran
split_data_dir.sh with the --per-utt option. That is only called from
a small number of splits. The solution is then to remove the split
directory and rerun the decoding.
If it does not appear in more than one of the utt2spk files, then
likely the problem is that you previously ran the decoding with a
different number of jobs, leaving higher-numbered .trans files there,
and the solution is to clean up that directory.
Dan