Slack messages are not sent to GitHub/GitLab
If messages from a specific developer are not sent to GitHub or GitLab, please try to refresh your GitHub or GitLab OAuth token. Axolo uses this token to write messages in your name. How to update your GitHub or GitLab OAuth token? Open Slack, Open the Axolo app home in Slack (click on the Axolo app in Slack, or cmd/ctrl + k then type 'Axolo'), Click on Update my GitHub/GitLab in the Settings category. , Click on Update my Slack in the Settings category.Some readersEnable Slack to create channels for Axolo. Restricted_action error.
Channel management in Slack In order for Axolo to create channels you need to accept those permissions into Slack. By default it is set to everyone, but in some workspaces admin can edit those settings. Here is how the Slack channel management settings looks like: Note: If this category doesn't appear it means you are not an owner of the workspace and that you don't have access to it.  or a Personal Access token. This guide will show you how to get it from GitLab and add it to your Axolo account. **1. Get your token from GitLab: ** Navigate to your Group seSome readersTroubleshooting: GitLab Webhook Issues
Issue: GitLab Stops Sending Webhooks to Axolo If you're experiencing issues where it appears that GitLab is no longer sending webhooks to Axolo, it could be due to delayed responses from our API. GitLab might discontinue sending webhooks if our API doesn't respond within their specified timeout period. Verify that your webhooks are failing in your GitLab Group Settings / Webhooks If you have a failing webhooks GitLab will show you an error here:  