[Retroactive] Actions workflow run logs delayed
Facts
- Source
- GitHub Status · original
- Started
- (31 days ago)
- Ended
- · lasted under a minute
- How it ended
- Microsoft marked it resolved.
- First captured by us
- Last changed
- (43 min ago)
Last text from Microsoft
On October 13, around 20:42 UTC, an infrastructure failure caused GitHub Actions to have delays showing logs for workflow runs. No logs were lost and the issue has now been resolved and log processing has caught up.
The actual workflows producing the logs were not impacted and ran normally and no run delays or check delays occurred.
Quoted from GitHub Status (source), captured . Reproduced for reporting and archival purposes.
Official updates
Posted by GitHub Status, newest first.
Resolved
On October 13, around 20:42 UTC, an infrastructure failure caused GitHub Actions to have delays showing logs for workflow runs. No logs were lost and the issue has now been resolved and log processing has caught up. The actual workflows producing the logs were not impacted and ran normally and no run delays or check delays occurred.
What Microsoft changed
Microsoft edits the text of an incident in place. We keep every version we capture (checked every minute) and highlight the difference. Removed text is struck through, added text is marked.
First version we captured
Captured · Microsoft's own timestamp · revisionzvwyt4qrOriginal text as we first saw it
On October 13, around 20:42 UTC, an infrastructure failure caused GitHub Actions to have delays showing logs for workflow runs. No logs were lost and the issue has now been resolved and log processing has caught up.
The actual workflows producing the logs were not impacted and ran normally and no run delays or check delays occurred.