Unable to view inline logs in test branch instantly. Same is working fine in master

[Jaspinderk18]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

With latest github UI changes, I'm unable to view inline logs instantly on a test branch. It appears after 10-15 mins Same is working fine in master. It was working fine yesterday

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

[NzKyle]

Can confirm that I'm seeing that same thing.

[yellowbonV]

Please fix this asap

[EchooWww]

Having the same issue, please fix this

[Ahmedhemaz]

Have the same issue

[robertkraig]

I am seeing this as well.

[robertkraig]

this might be the same issue, https://github.com/orgs/community/discussions/210224

[BenkhiraAhmedBaderEddine1]

1. Rule out the UI
   Hard refresh (Ctrl+Shift+R), or open the run in an incognito window with extensions disabled. Extensions that restyle GitHub, ad blockers and dark-mode tools can break the new log viewer.
   Check githubstatus.com for a Actions incident. Delayed or missing logs are a common symptom.
   If you’re in a UI preview or beta, try switching back to the classic view if the option exists.
2. Get the logs another way
   In the run page, use the menu → Download log archive (or “View raw logs” per step).
   With the CLI: gh run view --log. If the logs appear here but not in the UI, the logs are uploaded fine and it’s a rendering issue.
3. If it’s still delayed (ARC-specific)

Since you’re running ARC, the delay may be on the runner side:

Runner pod terminating too early. Ephemeral runner pods can be killed before the final log upload finishes, which would explain logs showing up 10–15 minutes later. Check the pod logs and events (kubectl logs, kubectl describe pod) for the runner around job end.
Network or proxy blocks. Make sure the runner can reach GitHub’s results and logging endpoints, such as results-receiver.actions.githubusercontent.com and *.actions.githubusercontent.com. A proxy or firewall that blocks or throttles them causes delayed or missing logs.
Version drift. Upgrade the ARC controller and runner image to the latest release. Outdated runner versions often misbehave after GitHub backend changes.
Resource pressure. If the runner pod is CPU- or memory-throttled on that branch’s jobs, log flushing can lag.
4. Why master works but the test branch doesn’t

Compare the two runs:

Are they using different runner groups, labels or scale sets, and so different pods or nodes?
Does the test branch’s workflow produce much larger or faster output, for example verbose build logs? Heavy output can delay streaming.
Is the workflow file different (a different runs-on, or a container: setting)?

Rerun the test-branch job on the same runner as master to see if the difference follows the runner or the branch.

5. Escalate if needed

If nothing above helps, add your findings to the GitHub Community discussion you screenshotted, including the run URL, ARC version, runner version, and whether gh run view --log shows the logs. That is usually what GitHub staff need to look into it.

If you share the ARC version, runner image and what gh run view --log shows, I can narrow it down further.