Skip to main content

​
Warrn asks me to connect my account

The workspace connection and your personal account link are separate:
  1. A Warrn admin or owner connects the Slack workspace from Settings > Integrations.
  2. Each responder opens the Warrn App Home in Slack and selects Link account.
Link the Warrn user that belongs to the same organization as the connected Slack workspace. Use Disconnect account in App Home if you need to replace the link.

​
I cannot connect the workspace

Only a Warrn admin or owner can start Slack OAuth. A Slack workspace can belong to only one Warrn organization at a time. If Slack reports that the workspace is already linked, ask the owner of the existing Warrn organization to disconnect it before trying again.

​
Warrn says the connection needs attention

Slack permissions can change after the app was installed. Go to Settings > Integrations, reconnect Slack, and approve the current permission set. Reconnect instead of creating another workspace connection. Your existing organization association is retained when the same workspace is authorized again.

​
A channel is missing from the notification picker

The OAuth notification picker lists public, unarchived channels. Confirm that the Slack workspace is connected, verify that the channel is public and active, then refresh the integration page. To send notifications to a private channel, configure a Slack Incoming Webhook for that channel. Reconnect the Slack app if Warrn reports missing permissions.

​
The assistant cannot read a channel

Warrn must have access to a channel before it can read its messages.
  • For a public channel, ask Warrn again and approve its request to join when prompted.
  • For a private channel, invite the Warrn app manually.
  • Ask the question from inside the relevant thread when you want Warrn to use that thread as context.

​
A command says it must be used in an incident channel

/update, /responder, /severity, /timeline, /postmortem, and /scribe require a channel associated with a Warrn incident. Move to the incident’s Slack channel and run the command again. Use /incident, /oncall, and /stats from any channel where Slack commands are available.

​
/responder cannot add someone

The selected Slack user must link their Slack identity to a Warrn account in the connected organization. Ask them to open the Warrn App Home and select Link account, then retry the command.

​
/postmortem shows no document

The command only displays an existing postmortem. Open the incident in Warrn and create its postmortem, then run /postmortem again.

​
/scribe cannot start

Run /scribe inside an incident channel. The incident must have a war-room URL. Create or attach a war room in Warrn, then retry. If Scribe is already active, the request completes without starting another session.

​
An alert or incident action fails

Confirm that:
  • Your Slack account is linked to the correct Warrn user.
  • You still have permission to perform the corresponding action in Warrn.
  • The alert or incident is still in a state where the action applies.
  • The Slack workspace connection does not require reconnection.
Open the item in Warrn to verify its current state. If the problem continues, contact support with the alert or incident identifier and the approximate time of the Slack action.