Skip to content

/actions/runs/{N}/jobs returns empty .jobs[] for completed runs #38286

Description

@mrramam

Gitea Version

1.25.5

What happened?

The REST API endpoint GET /api/v1/repos/{owner}/{repo}/actions/runs/{run_number}/jobs returns {"jobs":[],"total_count":0} (HTTP 200) for a workflow run that completed successfully and whose jobs + step logs are clearly visible in the web UI at ///actions/runs/{run_number} .

The asymmetry blocks programmatic log retrieval: even though the per-job log endpoint added in PR #33858 ( GET /actions/jobs/{job_id}/logs , shipped in v1.24.0) exists, it can't be used because the upstream listing endpoint never surfaces a job_id for these runs.

Notably, the run record itself is reachable via /api/v1/.../actions/tasks (so head_sha / run_number / status=success resolution all work) — only the per-run jobs listing is empty.

How are you running Gitea?

Docker — official gitea/gitea:latest image (Linux/Alpine inside), running on a macOS (Darwin) host. Image digest sha256:f846d26a…914472, built 2026-03-13

DB engine SQLite3

act_runner --version act_runner version v0.3.1

gitea version 1.25.5 built with GNU Make 4.4.1, go1.25.8 : bindata, timetzdata, sqlite, sqlite_unlock_notify

DEFAULT_ACTIONS_URL=self

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions