GitHub Pages repeatedly times out at syncing_files; website remains outdated

[zdenekbubak-glitch]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

Hello,

GitHub Pages deployments for my repository repeatedly stall at syncing_files and fail after 10 minutes with Timeout reached, aborting!. The website continues to serve yesterday’s content.

Repository: https://github.com/zdenekbubak-glitch/Vesmir
Website: https://kosmonovinky.cz/

Latest failed run:
https://github.com/zdenekbubak-glitch/Vesmir/actions/runs/42807825545

Earlier failed runs:
https://github.com/zdenekbubak-glitch/Vesmir/actions/runs/42790839283
https://github.com/zdenekbubak-glitch/Vesmir/actions/runs/42788977096
https://github.com/zdenekbubak-glitch/Vesmir/actions/runs/42787700313

Last successful run:
https://github.com/zdenekbubak-glitch/Vesmir/actions/runs/42708312492

Checks performed:

• Page generation and artifact upload succeed.
• The inspected artifact contains the missing November 10 article.
• It contains 1,819 entries, approximately 82 MB compressed and 110 MB unpacked, with no symbolic or hard links.
• Compressed size increased by only approximately 146 KB compared with the last successful deployment.
• Failed deployments include different commits.
• Workflows share a concurrency group and do not overlap.
• The workflow uses actions/upload-pages-artifact@v3 and actions/deploy-pages@v4.
• Setting a 30-minute timeout did not extend the wait: the action explicitly clamps it to 600000 milliseconds.

Similar reports were found:
https://github.com/orgs/community/discussions/212350
https://github.com/orgs/community/discussions/212557

A shared cause has not been confirmed. Could GitHub staff investigate whether Pages synchronization is stuck for this repository and advise how to safely restore publishing while preserving the existing website and custom domain?

Thank you.
Zdenek

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

[zdenekbubak-glitch]

Update: Publishing has now recovered without any further changes to the repository or workflow configuration.

A new deployment completed successfully:
https://github.com/zdenekbubak-glitch/Vesmir/actions/runs/42818281164

The website now displays all seven November 10 articles, and the previously missing article returns HTTP 200, including when accessed through the tracked link posted on X.

This suggests a transient GitHub Pages synchronization issue, although the root cause remains unconfirmed. If GitHub staff can identify the cause of the earlier failures, that would help us avoid unnecessary configuration changes in the future.

Thank you.