Each successful POST to the CI/CD hook starts a new Run. DoesQA does not merge duplicate pipeline calls. Unexpected test counts usually come from tags, recipes, or Flow Branches, not from a single POST splitting.

  1. Open Runs (Run History). Compare the Run IDs, timestamps, and trigger labels for the Runs you did not expect. Note whether more than one webhook title or label appears.
  2. In your pipeline, confirm only one job sends a POST. A GET is preview only and starts nothing. Retries, a second job, or a Schedule with the same tags each create another Run.
  3. Open Settings → CI/CD and confirm the key is Active. Check whether the request uses ids, recipe, withAll / withoutAny, or testsTagged.
  4. Send the same query as a GET preview. Compare the Flow and test counts with what you expect before you POST again.
  5. In each selected Flow, count Flow Branches and check Condition and Tag Test steps. Those change how many Test Cases a Run contains.
  6. If a Schedule and a pipeline both select the same Flows, pause or retarget one of them so only one trigger owns that set.

If the counts still look wrong after a clean POST, open Help in DoesQA and select Create new ticket. Include one Run ID from the unexpected set.

Related docs: CI / CD, Run Recipes, Run History and Run detail.