A team expects an agent execution job to reuse the state file produced by the planning job. The planning job completed successfully, but the execution job fails before running the agent. Which option best explains the behaviour? Select one answer.
Workflow: agent-state-handoff
Job: plan
Step: Upload state artifact
Uploaded artifact: agent-state
Artifact path: .agent-state/state.json
Job: execute
Needs: plan
Run actions/download-artifact@v4
with:
name: agent-state-v2
Error: Unable to find any artifacts for the associated workflow
Artifact name: agent-state-v2
Run ./scripts/run-agent --state ".agent-state/state.json"
Skipped because previous step failed.Choose an answer
Tap an option to check your answer.
Correct answer: The artifact name changed between jobs.
Why this is the answer
The plan job uploaded an artifact named agent-state. However, the execute job attempted to download an artifact named agent-state-v2. Since the names do not match, the actions/download-artifact@v4 action failed, leading to the subsequent steps in the execute job being skipped. The artifact name must be identical when uploading and downloading for the action to succeed. The job output context is not directly relevant here, as the problem is with the artifact name itself, not how a variable might be referenced. Permissions issues would typically manifest with a different error message indicating unauthorized access, not an inability to find the artifact by name. Agent state exceeding cache limits is also incorrect; the error clearly states the artifact could not be found, not that it was too large or expired from a cache.
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