[API] Logs for a workflow run are different between those downloaded from UI and through API

[akashchi]

Select Topic Area

Bug

Body

Hi,

I have a workflow run https://github.com/openvinotoolkit/openvino/actions/runs/13724145680 that has an error in one of the jobs, Jax Layer Tests.
When I go into the job tab and use the gear icon to Download log archive, I get the archive that contains full logs for the jobs in the .txt files, including the one with the error:

and this log file has the error that is present if viewed using the UI:

If I download the logs using the GitHub Actions API https://api.github.com/repos/openvinotoolkit/openvino/actions/runs/13724145680/logs, I get the following structure which is expected:

However, when I open the JAX Layer Tests JAX Layer Tests folder, I get this:

only one file, without the rest of the logs. All the successful jobs have full logs, for each step.

We have a system for log analysis and rely on the full logs to be present. Why are the log files not present in the archive if downloaded through API?

[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. ⭐