With the `trigger-parameterized-builds` macro/plugin does not have a switch which will automagically trigger jobs only if there are none in the queue. The way around this to use the manual way (without the plugin) to trigger builds and build some logic over checking if the jobs are in the queue before triggering. However, once a job is already in the queue (it already been triggered to start with some data from the older AR builds, which is probably outdated), and therefore should remove existing int/dist job from the queue before trigger adds a new int/dist job.  

If there is scope for some improvements, I think we should be fix this in both places. 

Thanks,

Anil