GitHub Actions logs missing and job step metadata empty for new runs

[Grizak]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Metrics & Insights

Discussion Details

Description

Since October 24, 2026, I'm experiencing an issue with the GitHub Actions UI where the normal step-by-step logs are no longer displayed for new workflow runs.

Instead, the job view displays a plain text block containing only messages such as "This job failed" or "This job succeeded", with dropdowns that remain expanded. The logs are not available while the job is running, and the usual log viewer formatting is missing.

Expected behavior

• Logs should be available while a job is running.
• Completed jobs should display their individual steps, with expandable log output and the usual formatting.
• The REST API should return the job's step metadata.

Actual behavior

For a recent run, the UI does not display the normal logs. The GitHub CLI also returns no output when attempting to retrieve logs.

More importantly, the REST API returns an empty steps array for completed jobs.

For example, querying:

GET /repos/Grizak/Wick/actions/jobs/120940200529

returns:

{
  "id": 120940200529,
  "status": "completed",
  "conclusion": "failure",
  "steps": []
}

The actual response contains the normal job metadata, including timestamps, runner information, and the conclusion, but no step details.

Reproduction details

• Repository: https://github.com/Grizak/Wick
• Affected run: https://github.com/Grizak/Wick/actions/runs/40116987576
• Example affected job: https://github.com/Grizak/Wick/actions/runs/40116987576/job/120940200529
• Workflow: Build & Release Wick
• Affected run started: October 24, 2026, at 17:37 UTC

I also checked an older run from October 22, which returns populated steps arrays through the same CLI command and whose logs are viewable in the browser. That run belongs to a different workflow, so it is a comparison rather than a controlled reproduction.

Troubleshooting performed

• Checked the workflow run metadata using gh run view.
• Queried the individual job through the GitHub REST API.
• Confirmed that the individual job API also returns an empty steps array.
• Compared the result with an older run where step metadata and logs are available.

Question

Is anyone else experiencing this issue? Could this be a regression affecting the creation or retrieval of Actions step metadata and logs for new workflow runs?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Grizak]

Ok, I just published this bug report and it seems that it has resolved itself while writing the bug report, so I should consider this a temporary issue and not a permanent bug, however, I still don't know if this is something github currently working on or if it's just some system that rebooted by itself