GitHub Pages deployment stuck – syncing_files timeout #212697
Replies: 2 comments
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
|
I looked at the public run data for embed-engine and the two things you see fit together. Run #575 does have jobs, they just don't show up in the default jobs list. The actual problem is the deploy step stopping at about 10 minutes in both #574 and #575. That's the deploy-pages timeout ( What I'd do:
Can you check the log of the "Deploy to GitHub Pages" step in #575? If the last lines say "syncing_files" over and over, that's the case above. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Workflow Deployment
Discussion Details
Please note an additional inconsistency:
GitHub sent a failure notification for workflow run #575, reporting that the build succeeded in 18 seconds but deployment failed after 10 minutes and 13 seconds.
However, the GitHub Actions API continued to report the same workflow as
queued, with no jobs returned.Please investigate this inconsistent state and clear any stale Pages deployment or workflow lock affecting repository
radimventus/embed-engine.The previous workflow #574 also completed its build successfully but failed during deployment after approximately 10 minutes.
All reactions