Getting 400 error on Slack Integrations
See original GitHub issueI am receiving this error while trying to run the actions in one of my org’s private repo.
Error: Request failed with status code 400
Our team Fyle has sponsored the project thinking it might add value but it keeps giving a 400 bad request whenever run. Attaching a screenshot of the logs here.
Let me know if there are any permissions that need to be enabled for sending the message to slack.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Troubleshooting "(400) Bad Request" return from Slack API
The messages have formatting and use some links. Recently, some messages stopped to get through, returning (400) Bad Request.
Read more >Webhooks for slack integration is throwing 400 error #770
I got the same, slack returns. Response headers: Content-Type: text/html. Transfer-Encoding: chunked. Connection: close
Read more >Sending messages using Incoming Webhooks - Slack API
Incoming webhooks return more expressive errors than our Web API, including more relevant HTTP status codes (like "HTTP 400 Bad Request" and "HTTP...
Read more >Upon Slack installation, why am I seeing a 400 error ... - Nightfall
Upon Slack installation, why am I seeing a 400 error mentioning a "Restricted Action"? Understand why Channel Management Restrictions in your Slack Workspace ......
Read more >Webhook Error: HTTP Error 400: Bad URL request
A 400 error message usually means that the request was malformed. In other words, the data stream sent by the client to the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@anshsrtv sorry for the late reply.
Review time is calculated as the moment of the first review minus the most recent date between the last commit and the time the PR was published. You can check it here. The logic behind this is, somebody might publish the PR first but keep adding commits before requesting for reviews.
Sounds like a good idea. I’ll make some time to launch this feature this week 😉
Thanks for the update @anshsrtv, I’ll add this to the “troubleshooting” section.
As an alternative, if you need the stats for the lasts 30 or more days, you could use the
limit
option. This way the stats still calculated for the desired time frame but the message is limited to the first X rows to fit the Slack limitation.Unfortunately Slack blocks does not support tables yet. That’s a huge limitation to make it looks the same than Github. The only option would post them as an image, but it would loose more important capabilities like copying text, and using links.
However, Slack still improving their Blocks API, I hope anytime soon they support tables and I could migrate to that format then.