troubleshooting-aws-device-farm-runs
Troubleshooting AWS Device Farm Runs
Overview
Diagnoses why an AWS Device Farm run, job, suite, or test failed, errored, was
skipped or stopped, or passed when it should have failed, and why an upload or a
ScheduleRun call fails. The evidence is almost always already in the account:
API fields, upload records, device pool rules, and the artifacts of the run that
failed. This skill says which artifact holds the evidence for each symptom and
how to correlate artifacts into a root cause and a user-side fix.
Works best with the AWS MCP server — recommended for sandboxed command
execution and audit logging. All guidance also works with standard AWS CLI
access. Device Farm's API is only in us-west-2, so pass --region us-west-2.
Reading artifacts needs a shell with a download tool and unzip; without one,
the user can download the same files from the job's page in the Device Farm
console.