same here

Hey there!
Are you able to check your browser's network tab for a trace ID? Would love to investigate it there

Could you also provide a screenshot with what you're seeing related to triggering redeploys/new deploys?

For me

Details:

- When clicking "Deploy latest commit" from the command palette (Cmd+K), I get either:

- Error: "Failed to trigger deployment - Problem processing request"

- Or nothing happens at all

- The current ACTIVE deployment is from 4 hours ago (commit 1efe559e - "fix(i18n): add linktree-alternatives to 13 m...")

- All recent commits are in railway, not trigged

- The GitHub webhook appears to not be working (commits not showing in the list)

Project Info:

- Project ID: eae55430-f659-445c-bffe-c257e69de993

- Service ID: a055ee31-6076-4916-a4dc-b3ba4ebc2eab

- Environment: production (europe-west4-drams3a)

- Branch: kleap-migration

- Domain: kleap.co

Could you move this to your own thread and link it here? Would love to get a bit more info there if possible this is absolutely perfect thank you!

Here

And in CLI: Bash(railway redeploy -y 2>&1) timeout: 1m 0s

⎿ Error: Exit code 1

Failed to fetch: error sending request for url (https://backboard.railway.com/graphql/v2)

Caused by:

0: error sending request for url (https://backboard.railway.com/graphql/v2)

1: operation timed out

Thanks that is extremely helpful! We're in the process of rolling something out which should resolve this. Will notify when done and when you should try again.

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

Hey there!
We just pushed a fix and this should be good to go now. Can you try again and let me know how it works?

✅ The ticket GitHub integration deployment issues has been marked as completed.

It works, godbless

Hey y'all, relaying what I shared with another customer apologizing for the delayed ack from our side. This one was compounded by 3 co-morbid issues happening at the same time which made it diagnose, plus with the recent user growth, the magnitude of failiures meant that our traditional alerting didn't warn us until the public user base alerted us to the severity of the issue. Sorry about that everyone.