A team expects an agent workflow to run when an issue receives the agent-ready label. The issue was labeled by a maintainer, but no workflow run appears. Which option best explains the behaviour? Select one answer.
Repository event:
Event: issues
Action: labeled
Issue: #284
Label added: agent-ready
Actor: octocat-maintainer
Workflow file: .github/workflows/invoke-agent.yml
Configured trigger:
on:
workflow_dispatch:
inputs:
issue_number:
required: true
run_mode:
required: true
Actions result:
No workflow run was created for this issue event.
No check suite was created.
No job logs are available.Choose an answer
Tap an option to check your answer.
Correct answer: The workflow only supports manual dispatch.
Why this is the answer
The workflow's on: workflowdispatch trigger means it can only be started manually through the GitHub UI, API, or GitHub CLI. It is not configured to respond to repository events like an issue being labeled. Therefore, even though the agent-ready label was added, the workflow did not automatically run. To trigger on a label, the workflow would need an on: issues: types: [labeled] trigger. The other options are incorrect because permissions, branch filters, or secret availability are not relevant when the workflow itself isn't configured to run on the specified event.
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