I should start off by saying that I tried to find information on the web related to this issue, but was not able to. So I apologize if this is a duplicate bug report.

I currently have a Jenkins job, "Rollup_Stage", that uses the parameterized trigger plugin to call multiple child jobs ("Deploy_iOS_IPA" and "Deploy_Stage"). Here is the screenshot:

This configuration worked consistently for a long time, but in the past month we have noticed a strange behavior. This issue is happening more and more frequently over time.

The issue is that the parent job thinks it called the child job, but the child job never gets triggered.

For example, this is the what we're seeing on the parent job "Rollup_Stage":

Notice that it thinks it started "Deploy_Stage":

However, if you look at this screenshot which shows the build history for "Deploy_Stage" you will notice that "Deploy_Stage" never started:

What's strange is that the other job "Deploy_iOS_IPA" is consistently running as expected, but from some reason the "Deploy_Stage" job is not starting.

Any advice on how to diagnose and resolve the issue would be appreciated.