a year ago
Hey, The Slack webhook is throwing Request failed, i have created a new webhook as well and still getting the same when i test it, it says "Request failed"
.
Initially it was showing Deprecated when i faced the issue and Railways said me to fix it , a button appeared and now i am getting "Request failed"
8 Replies
a year ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 Blocking Webhooks POST Payloads (Whapi.cloud) on Production URL - Empty Payload
- 📚 Webhooks
- 🧵 server closed the connection unexpectedly
If you find the answer from one of these, please let us know by solving the thread!
a year ago
I am experiencing the same problem
a year ago
I got two updates in Slack but those were old as i already deployed the code by moving to the dashboard and approved the PR but after 1 hour i got a notification "PENDING APPROVAL"
a year ago
Hello,
I have tested this on our my end and am currently unable to reproduce this issue. Things appear in order!
I will note (something I need to look into) the "test" feature shows that "request failed" even though actual events go through. Other then that, I'll open this up to the community to help debug.
Status changed to Awaiting User Response Railway • 11 months ago
10 months ago
I am also having this issue
10 months ago
Also, I'm getting same issue on test slack webhook - Request failed
10 months ago
Thanks for pointing this out. The "Test" button for webhooks sends a fetch request directly from your browser, so any CORS restrictions set (or not set) by Slack will apply. This can result in a "Request failed" message, even if the webhook itself is working correctly for actual events triggered by Railway. If your real notifications are coming through as expected, you can safely ignore the test error. If you're not seeing any real notifications, let us know, and we can dig deeper.
