ContextQMD
Back to Gitlabhq

Troubleshooting GitLab for Slack app

doc/user/project/integrations/gitlab_slack_app_troubleshooting.md

19.2.05.5 KB
Original Source

{{< details >}}

  • Tier: Free, Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated

{{< /details >}}

When working with the GitLab for Slack app, you might encounter the following issues.

App does not appear in the list of integrations

The GitLab for Slack app might not appear in the list of integrations. To have the GitLab for Slack app on your GitLab Self-Managed instance, an administrator must enable the integration. On GitLab.com, the GitLab for Slack app is available by default.

Error: Project or alias not found

Some Slack commands must have a project full path or alias and fail with the following error if the project cannot be found:

plaintext
GitLab error: project or alias not found

To resolve this issue, ensure:

Slash commands return dispatch_failed in Slack

Slash commands might return /gitlab failed with the error "dispatch_failed" in Slack.

To resolve this issue, ensure an administrator has properly configured the GitLab for Slack app settings on your GitLab Self-Managed instance.

Notifications not received to a channel

If you're not receiving notifications to a Slack channel, ensure:

App Home does not display properly

If the App Home does not display properly, ensure your app is up to date.

Error: This alias has already been taken

You might encounter error 422: The change you requested was rejected when trying to set up on a new project. The returned Rails error might be:

plaintext
"exception.message": "Validation failed: Alias This alias has already been taken"

To resolve this issue:

  1. Search in your namespace for projects with similar names and have the GitLab for Slack app enabled.
  2. Check among these projects for those with the same alias name as the failed project.
  3. Edit the alias, make it different, and retry enabling GitLab for Slack app for the failed project.

GitLab Duo @mention failures

When you @mention the GitLab app in Slack to trigger GitLab Duo, the app posts a message back to the thread if something goes wrong. Use the message text to identify the cause and apply the fix.

Slack messageCauseFix
Lock emoji (🔒) and an authorization promptYour Slack account is not linked to a GitLab account.Complete the authorization flow to link your Slack and GitLab accounts.
"You do not have access to this feature yet"The slack_duo_agent feature flag is not enabled for your account.Ask an administrator to enable the feature flag for your user.
"This feature requires GitLab Duo Agent Platform"Your account does not have a GitLab Duo Agent Platform license.Check your GitLab Duo entitlement with your administrator.
"Set your default Duo namespace in your preferences"Your GitLab account has no default Duo namespace configured.Set a default Duo namespace in your GitLab preferences. On GitLab.com, you must have an active GitLab Duo add-on seat in the namespace.
"The Duo Developer flow is not enabled for your namespace"The foundational Duo flow is not enabled for your namespace.Ask a group owner to enable the flow in GitLab Duo Agent Platform settings.
"Could not set up the service account…"The service account for your namespace could not be provisioned.Check your namespace GitLab Duo configuration and service account provisioning.
"Could not set up the workspace project…"GitLab could not find or create the duo-workspace project in your namespace.Verify that you can create projects in the namespace. Your role and the namespace project_creation_level setting must allow project creation.
"Failed to start the Duo Developer workflow" or "Something went wrong…"The Duo flow trigger or execution failed.Check the CI job logs and GitLab integration logs for details.

Debugging tips for GitLab Duo @mention

  • Integration logs are written to integrations_json.log. Each entry includes the slack_workspace_id field, and often slack_user_id and channel_id. Filter by slack_workspace_id to find entries relevant to your workspace.
  • Sidekiq worker logs (sidekiq.log) also include slack_workspace_id and slack_user_id for Integrations::SlackEventWorker jobs. Use these to trace whether the event was received and processed.
  • If the bot cannot react or reply at all, the issue is likely with the Slack integration configuration or bot token. Check integrations_json.log for entries with "message": "SlackInstallation record has no bot token". If the bot reacts but then posts an error, the issue is with the user-side authorization gates or namespace resolution.
  • The duo-workspace project is created automatically the first time a flow runs and reused afterward. If project creation fails, use a namespace where you have at least the Maintainer role, or ask a group owner to adjust the project_creation_level setting.