capabilities.work

Inspect Failed Job Logs

A 4-step recipe with GitHub Actions. We can help you get access.

Recipe · 4 steps

Inspect Failed Job Logs

with GitHub Actions · Continuous Integration Management
Works with AI assistants

Resolve the log download URL for a job in the latest failed run.

  1. List the repository's runs filtered to the failure status and capture the newest failed run id. Branch to the end when there are no failures.
  2. List the jobs of the failed run and capture the id of the first job.
  3. Fetch the first job to confirm its conclusion and name before pulling its logs.
  4. Request the job log file. The API responds with a 302 redirect to a short-lived download URL.
What you'll need to have ready
  • accessToken: GitHub bearer token with read access to the repository.
  • owner: The account owner of the repository.
  • repo: The name of the repository without the .git extension.
For your developer

Arazzo workflow github-actions:inspect-failed-job-logs, 4 operations: listWorkflowRunsForRepo → listJobsForWorkflowRun → getJobForWorkflowRun → downloadJobLogsForWorkflowRun. Specs on APIs.io.

More recipes with GitHub Actions

Approve a Pending DeploymentCancel a Workflow Run and ConfirmCollect Workflow Run ArtifactsDispatch and Track a Workflow RunPrune Repository CachesRegister a Self-hosted RunnerRe-run Failed Jobs and TrackShare an Organization Secret with Selected RepositoriesUpsert a Repository SecretUpsert a Repository Variable