Two Copilot agent tasks update different services in the same monorepo. Each task opens a draft pull request. The validation workflow is expected to keep their runs separate, but one run cancels the other. Which option best explains the issue? Select one answer.
Workflow: validate-agent-pr
Event: pull_request
Base branch: main
PR #618
Head branch: copilot/api-timeout-fix
Concurrency group: agent-validation-main
cancel-in-progress: true
Status: cancelled
PR #619
Head branch: copilot/ui-empty-state-fix
Concurrency group: agent-validation-main
cancel-in-progress: true
Status: in_progress
Branch protection:
Required check: validate-agent-pr / test
PR #618 status: Expected — Waiting for status to be reportedChoose an answer
Tap an option to check your answer.
Correct answer: Both PRs share the same concurrency group.
Why this is the answer
The issue arises because both pull requests (PRs) share the same concurrency group: agent-validation-main. When cancel-in-progress: true is set for a concurrency group, any new workflow run in that group will automatically cancel any existing run that is still in progress within the same group. In this scenario, PR 619's workflow run started, found an active run for PR 618 in the agent-validation-main group, and consequently canceled it. To prevent this, each PR should have a unique concurrency group, perhaps by including the PR number or head branch name in the concurrency group definition, e.g., agent-validation-${{ github.headref }}. The draft PR state, bot permissions, or artifact paths are not directly causing this cancellation behavior.
Pass your exam — without the endless answer hunt
Get every verified question and explanation for this exam in one place, and save hours of prep. 1,000+ certifications · 20+ languages · free to start.
Pass your exam faster → No card needed