Similar to JENKINS-23142, however, I experience this problem with different parameters.

After calling GET jenkins/job/jobname/buildWithParameters?profile=1

A job is scheduled into the queue.

However, after calling this again with a different parameter

After calling GET jenkins/job/jobname/buildWithParameters?profile=2

A new job is not scheduled. instead the queue adds "caused by" element, but no new item is created.

Currently running Jenkins 2.13

{{<queue _class="hudson.model.Queue">
<item _class="hudson.model.Queue$BlockedItem">
<action _class="hudson.model.ParametersAction">
<parameter _class="hudson.model.StringParameterValue">
<name>PROFILE</name>
<value>automated-testing</value>
</parameter>
</action>
<action _class="hudson.model.CauseAction">
<cause _class="hudson.model.Cause$RemoteCause">
<shortDescription>Started by remote host 10.20.10.49</shortDescription>
<addr>10.20.10.49</addr>
</cause>
<cause _class="hudson.model.Cause$RemoteCause">
<shortDescription>Started by remote host 10.20.10.49</shortDescription>
<addr>10.20.10.49</addr>
</cause>
<cause _class="hudson.model.Cause$RemoteCause">
<shortDescription>Started by remote host 10.20.10.49</shortDescription>
<addr>10.20.10.49</addr>
</cause>
<cause _class="hudson.model.Cause$RemoteCause">
<shortDescription>Started by remote host 10.20.10.49</shortDescription>
<addr>10.20.10.49</addr>
</cause>
</action>
<blocked>true</blocked>
<buildable>false</buildable>
<id>5</id>
<inQueueSince>1468429276794</inQueueSince>
<params>PROFILE=automated-testing</params>
<stuck>false</stuck>
<task _class="com.cloudbees.plugins.flow.BuildFlow">
<name>corporate-deploy-merged-apis</name>
<url>
http://bos-repohr64.jenzabar.net:8080/job/corporate-deploy-merged-apis/
</url>
<color>red_anime</color>
</task>
<url>queue/item/5/</url>
<why>Build #145 is already in progress (ETA:17 min)</why>
<buildableStartMilliseconds>1468429285910</buildableStartMilliseconds>
</item>
</queue>}}

I tried starting this job manually via UI, and it correctly schedules a new job.