Dash0 acquires Polar Signals

Last updated: October 1, 2026

Troubleshoot Slack Integration

Solutions to common issues with Agent0 mentions, Slack automations, and Slack tools.

Solutions to common issues when using Slack with Agent0.

When You Mention Agent0

Issues you can hit when you tag @dash0 in a channel. See Ask Agent0 in a Slack Channel for how mentions work.

Agent0 Asks You to Connect Your Account

Agent0 says: it needs to know who you are in Dash0, and sends you a private message.

Common causes:

  • Your Slack account is not connected to a Dash0 account yet.
  • The connection is no longer confirmed.

Fix: Open the private message from Dash0, follow the link, confirm, then mention Agent0 again.

Agent0 Asks Which Data to Use

Agent0 says: it does not know which Dash0 data to look at, and shows a Configure Dash0 button.

Common causes:

  • The channel, or your direct message, is not pointed at an organization and dataset yet.

Fix: Click Configure Dash0, pick the organization and dataset, and submit. Agent0 answers your original question afterwards. In a channel the choice applies to everyone there. In a direct message it applies only to yours.

Agent0 Doesn't Reply at All

Common causes:

  • In a channel, the bot isn't a member.
  • The message matched an enabled Slack automation trigger, so the automation ran instead of Agent0 answering the question.
  • The mention came from another bot or from an automation's own message. Agent0 only answers people.

Fix:

  1. Type @dash0 in the channel. If the bot appears in autocomplete, it's a member. If not, run /invite @dash0.
  2. Check your organization's automations for a Slack message trigger whose keyword appears in your message. Rephrase, or use a channel the automation doesn't cover.

Agent0 Says Your Account Isn't a Member of the Organization

Common causes:

  • Your Dash0 account exists, but it isn't a member of the organization this channel is pointed at.

Fix: Ask a Dash0 admin to add you to the organization, or point the channel at an organization you're a member of.

Agent0 Says the Workspace Isn't Connected to the Organization

Common causes:

  • The channel is pointed at an organization whose Slack integration has since been disconnected.

Fix: An admin reconnects the integration in Settings → Integrations, or someone reconfigures the channel with Configure Dash0.

Agent0 Says No Organizations Are Associated with the Workspace

Common causes:

  • The Dash0 Slack app is installed, but the workspace isn't connected to any Dash0 organization.

Fix: An admin connects the workspace in Settings → Integrations. See Set Up Slack Integration.

Agent0 Says It Couldn't Reach Dash0

Common causes:

  • A temporary problem checking your connected account.

Fix: Mention Agent0 again in a moment. If it keeps failing, contact Dash0 support.

The Answer Takes a Long Time

Symptoms:

  • The progress card stops updating and says the run is taking a while.

Fix: Wait for the answer. If nothing arrives, ask again with a narrower question: one service, one shorter time range.

Agent0 Misses Earlier Messages in a Long Thread

Common causes:

  • Agent0 reads up to 50 replies per mention. Older messages in a very long thread are left out.

Fix: Repeat the important details in your question, or start a new thread.

Automations and Slack Tools

Automation Doesn't Trigger from Slack

Symptoms:

  • You post a message matching the keyword.
  • The automation doesn't run.

Common causes:

  • The Dash0 bot isn't in the channel.
  • The automation is disabled.
  • The keyword match is incorrect.

Fix:

  1. Verify the bot is in the channel: check the member list or type @dash0.
  2. If not, invite the bot: /invite @dash0.
  3. Ensure the automation is Enabled in the automation editor.
  4. Check the Message Keyword field for typos or case issues (match is case-insensitive).
  5. Review the automation's run history for errors.

See Automation Doesn't Trigger for detailed troubleshooting.

Slack Tools Fail with Authentication Errors

Symptoms:

  • The automation triggers successfully.
  • slackSendMessage or other Slack tools fail with "authentication error" or "invalid token".

Common causes:

  • The Slack bot token was revoked (e.g., the app was removed from your workspace).
  • The integration was disconnected.

Fix:

  1. Go to Settings → Integrations in Dash0.
  2. Check if Slack shows as Connected.
  3. If not, click Connect and reauthenticate.
  4. If it shows as connected, try disconnecting and reconnecting to refresh the token.

Dash0 Says the Slack App Needs Updating

Symptoms:

  • Dash0 shows "An organization admin needs to update the Slack app to the latest version to enable all features."
  • Slack tools are unavailable and Agent0 does not answer mentions, but alert notifications still arrive.

Common cause:

  • The workspace was connected before the Agent0 scopes existed, so the install grants only the alerting scopes.

Fix:

Messages Post to Wrong Channel

Symptoms:

  • Agent0 posts messages to a different channel than expected.

Common causes:

  • The prompt doesn't specify which channel to use.
  • Agent0 is choosing a channel based on context.

Fix:

  • Explicitly specify the channel in your prompt: Post to #incidents using slackSendMessage with channel: incidents.
  • Use the {{slack.channel.name}} variable to reply to the channel where the trigger fired.

Bot Can't Post to Channel

Symptoms:

  • slackSendMessage fails with "channel_not_found" or "not_in_channel" error.

Common causes:

  • The bot isn't a member of the target channel.

Fix:

  1. Open the target channel in Slack.
  2. Invite the bot: /invite @dash0.
  3. Retry the automation.

Thread Replies Don't Work

Symptoms:

  • Agent0 posts a top-level message instead of replying in thread.

Common causes:

  • The prompt doesn't specify the threadTimestamp parameter.
  • The {{slack.message.timestamp}} variable isn't populated (wrong trigger type).

Fix:

  • Verify you're using a Slack message or reaction trigger that populates {{slack.message.timestamp}}.
  • Explicitly instruct Agent0 to reply in thread: Use threadTimestamp: {{slack.message.timestamp}} when calling slackSendMessage.

Further Reading