failed deployment

[mroswell]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

I've been getting this all morning when trying to deploy my latest commits:

Run actions/deploy-pages@v5
(node:2161) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Fetching artifact metadata for "github-pages" in this workflow run
Found 1 artifact(s)
Creating Pages deployment with payload:
{
	"artifact_id": 8070076261,
	"pages_build_version": "101be315453474ae00a05d44572267eb2d4c68e8",
	"oidc_token": "***"
}
Created deployment for 101be315453474ae00a05d44572267eb2d4c68e8, ID: 101be315453474ae00a05d44572267eb2d4c68e8
Getting Pages deployment status...
Error: Deployment failed, try again later.

The GitHub status page notes no issues, but I haven't been able to successfully deploy anything on TrialProtocols.com (https://github.com/mroswell/trialprotocols) for at least an hour.

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

[Kunal241207]

It looks like the deployment is being created successfully, but it's failing while GitHub Pages is trying to publish it. The punycode deprecation warning is unrelated and shouldn't be the cause.

Have you tried rerunning the workflow after a few minutes? Also, is this happening only in this repository or across multiple repositories? If it's affecting multiple repos, it could be a temporary GitHub Pages issue even if the status page isn't reporting anything.

If you can share the workflow run link or your Pages configuration, it might help narrow it down.

[mroswell]

Workflow run links:
https://github.com/mroswell/trialprotocols/actions/runs/28669627301
https://github.com/mroswell/trialprotocols/actions/runs/28664329699

Both are failing. One was Claude's attempt to deploy a trivial commit, and one is the actual code that I'm trying to deploy.

I haven't tried to deploy anything to other repos today.

[Kunal241207]

Looking at both runs, the build completes successfully and the github-pages artifact is generated in both cases. The failure only happens during the deploy job, so it doesn't look like an issue with your site or the workflow itself.

Since even a trivial commit shows the same behavior, this points more toward a GitHub Pages deployment issue than a problem with your code. I'd check whether deploying another repository works, just to confirm if it's repository-specific or affecting Pages more broadly.

[ahhh]

I'm also getting failed github page deploys, feels like the service is degraded but the status page isn't reflecting that...

Run actions/deploy-pages@v5 (node:2306) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. (Use node --trace-deprecation ... to show where the warning was created) Fetching artifact metadata for "github-pages" in this workflow run Found 1 artifact(s) Creating Pages deployment with payload: { "artifact_id": 8070542448, "pages_build_version": "6acbd85d37a2e9390337fe45ba00fe0bd30060c7", "oidc_token": "***" } Created deployment for 6acbd85d37a2e9390337fe45ba00fe0bd30060c7, ID: 6acbd85d37a2e9390337fe45ba00fe0bd30060c7 Getting Pages deployment status... Error: Deployment failed, try again later.

[mroswell]

Have you had any success yet? Still stuck for me.

[ThePhantom-S]

The "Deployment failed" error during the status check is a common, transient issue with GitHub Pages infrastructure. It is almost certainly not caused by your code.

Troubleshooting Steps

• Wait it out: The deployment service is likely experiencing a temporary backlog. Retrying in an hour usually resolves it.
• Validate Permissions: Ensure your workflow file contains the necessary permissions:

  permissions:
    contents: read
    pages: write
    id-token: write

• Trigger a fresh attempt: Push a trivial commit (like adding a newline to your README.md) to force the workflow to restart.
• Check Environment Status: Go to Settings > Environments in your repository to see if a specific deployment is "stuck" or "in progress," which confirms the service-side delay.

Next Steps

If this persists beyond 24 hours, contact GitHub Support to clear a "wedged" deployment status on your account.

Are you seeing these failures consistently across all branches, or just on the main branch?

[mroswell]

how to contact GitHub support?

[ThePhantom-S]

To contact GitHub Support, use their official portal. Note that they do not offer phone-based technical support.

Steps to Submit a Ticket

1. Visit: Go to support.github.com.
2. Sign In: Authenticate with your GitHub account.
3. Open Request: Select the relevant category (e.g., "GitHub Actions" or "Pages").
4. Provide Details: Include your Workflow Run URL, the specific repository name, and describe the "wedged" deployment state.

Tips for Faster Resolution

• Include Evidence: Attach your raw workflow logs.
• Be Specific: Explicitly state that you are experiencing a "wedged" deployment status during the actions/deploy-pages@v5 status check.
• Community Alternative: If you are on a free plan, you can also post your issue in the GitHub Community Discussions to see if others are experiencing the same localized outage.

Note: GitHub Support is available 24/7. You will receive an email confirmation from a @github.com address once your ticket is submitted.

[mroswell]

The issue is resolved.

The fix seems to be something my AI did. here are some notes from my Claude Code session:

What worked

The wedged workflow runs couldn't be canceled, force-canceled, or deleted (409 / 403 responses). But GitHub Pages has a separate legacy build endpoint — POST
/repos/OWNER/REPO/pages/builds — that bypasses the workflow queue entirely and triggers a direct Pages build. That's what did it.

Summary of what unblocked it

• The wedged workflow runs are still stuck in GitHub's Actions queue (both showing "queued" with 0 jobs). Those aren't harming anything now — just orphans that GitHub will eventually
  clean up.
• The Pages Status API had it as errored even while the public status page said "operational" — that mismatch was a strong signal something was broken.
• POST /repos/OWNER/REPO/pages/builds is the legacy-Pages manual-build endpoint. It bypasses the Actions dispatcher entirely and directly triggers a Pages build. Since your site is on
  build_type: legacy (branch-based deployment, not workflow-based), this endpoint actually works.
• The build took 18.1 seconds and everything's live at the correct URLs.

Handy commands to save

If this happens again on a legacy-Pages site:

check status

gh api /repos/OWNER/REPO/pages

force a rebuild bypassing stuck workflows

gh api -X POST /repos/OWNER/REPO/pages/builds

[ThePhantom-S]

That is great to hear, Thank you for the update.