If the seed job runs and updates a maven job that is already executing then all modules that have not built for that job are marked as 'not built' which then causes those artifacts to not be fingerprinted correctly. Looking at the console output for the job, it continues to execute correctly, but something about updating the job from the seed job causes it to break.