Unexpected behaviour when upgrading AppV 5.0 SP1 sequences

Unexpected behaviour when upgrading AppV 5.0 SP1 sequences
One of my students noticed some unexpected behaviour when upgrading an AppV 5.0 sequence for the second time. I haven’t run into this unexpected behaviour earlier because normally I make a new sequence every single time. In AppV 4.x the standard behaviour was to append the internal version number associated with the sequence to the .sft output file. ...