Hi Railway team,

I need human escalation. My previous thread was marked as solved by the bot, and a new thread was closed as duplicate, but production is still down.

This is not just a GitHub webhook issue anymore.

Project:

• Project ID: 869012b9-61e0-42d5-8a71-9982945aae5d

• Environment: production

• Workspace: polypropicks

• Plan: Hobby

• Services:

  • PREMVP
  • signal-cache-cron

• Repo: POLYPROPICKS/PREMVP

• Branch: main

Current production issue:

• PREMVP production is not correctly restored.
• https://polypropicks.com/ is not serving the app correctly.
• /api/feed/landing-cards?limit=1 is not returning the expected Next.js API response.
• Previous attempts to deploy/redeploy after the Railway incident either failed, were paused, or produced a broken runtime.
• Emergency railway up caused Railway/Railpack to run Caddy/static runtime instead of Node/Next.js, resulting in 404/502 behavior.

What happened:

• We upgraded from Trial to Hobby.
• Deployment actions were still unreliable/paused during the incident.
• A previous bot response said deployments succeeded, but the actual production app is still not working.
• A duplicate support thread was auto-closed, so I need this escalated rather than auto-resolved.

What we need urgently:

1. Please reopen/escalate the original issue to a human engineer.
2. Please restore PREMVP to a known-good GitHub-based deployment, or force deploy the latest GitHub commit cleanly from main.
3. Please confirm why Railpack is creating/running Caddy/static runtime for a Next.js app.
4. Please tell us whether our Hobby workspace is still affected by paused deployments/build backlog.
5. Please provide an exact recovery path.

Please do not mark this as solved automatically. Production is still blocked.