Analyzer gets confused about retry number in hierarchical workflows

Sometimes I see hierarchical workflows failing and when analyzer is run it says something like:

===============================merge.sh_ID0051714===============================

 last state: POST_SCRIPT_FAILED
       site: condorpool
submit file: merge.sh_ID0051714.sub
output file: 04/01/merge.sh_ID0051714.out.049
 error file: 04/01/merge.sh_ID0051714.err.049


However, there are no *.049 files yet. In the latest case, it was only up to 024.