Skip to main content
Last updated on

Troubleshoot the Slack Access and Integration Logs connector

Beta

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.

This page describes common errors you might encounter with the managed Slack Access and Integration Logs connector and how to resolve them.

Slack API rate limited​

Error message:

Slack API rate limited. Please retry the pipeline after some time.

or

Rate limit exceeded for Slack API. Please retry the pipeline after some time.

Cause: Slack rate-limited the connector's API calls. Slack returns this either as a ratelimited response body or an HTTP 429.

Solution:

Wait, then re-run the pipeline. If this happens repeatedly, reduce the pipeline's schedule frequency or the number of concurrent pipelines that share the same Slack OAuth app.

Slack API temporarily unavailable​

Error message:

Slack API is temporarily unavailable. Please retry the pipeline after some time.

Cause: Slack returned a transient service_unavailable response or an HTTP 503.

Solution:

Wait, then re-run the pipeline. If the issue persists, check Slack's status page.

Slack API token expired​

Error message:

Slack API token expired. Refreshing token and retrying.

Cause: The OAuth user token has expired and must be refreshed.

Solution:

The connector refreshes the token and retries automatically. If the error persists across multiple pipeline runs, edit the Unity Catalog connection and re-authenticate by signing in to Slack again.

Slack API returned an unrecognized error​

Error message:

Slack API returned an unrecognized error: <error>

Cause: Slack returned an error that the connector doesn't classify as transient. The <error> placeholder shows the raw error string from Slack (for example, missing_scope, not_authed, account_inactive, invalid_auth).

Solution:

Resolution depends on the specific error:

  • missing_scope — The Slack OAuth app is missing the admin user scope. Re-create the app with the admin scope under User Token Scopes, reinstall it, and recreate the Unity Catalog connection. See Configure authentication to Slack.
  • not_authed / invalid_auth — The token is invalid. Edit the Unity Catalog connection and re-authenticate by signing in to Slack as a Workspace Owner or Workspace Admin.
  • account_inactive — The Slack user that authorized the connector has been deactivated, or their Workspace Owner / Workspace Admin role was downgraded. Re-authenticate the Unity Catalog connection with a qualifying admin user.
  • For other error strings, see the Slack API error documentation.
On this page