My intent is to figure out if there is a way to monitor a job invocation accurately by either using the Queue ID returned as part of the Location and then retrieving the Build ID OR by passing a unique identifier to the Cause parameter.
What I find weird is that when there is a Quiet period in effect neither the Queue ID nor the Cause parameter behave as expected. Please see the attached sample test harness and its output.
There are 3 jobs invoked in parallel each a unique identifier for cause. This is is the outcome.
A. First job gets a successful build, the other 2 don't (presumably because of the Quiet period).
B. The First job is queryable through the Queue ID and the response does have the unique identifier passed in Cause.
C. However the second and third invocations get a status of 201 and have the same Queue ID of the first, with the response having all the 3 causes.