zeroclaw-labs/zeroclaw · error · anyhow::Error

Slack reactions.add failed ({status}): {sanitized}

Error message

Slack reactions.add failed ({status}): {sanitized}

What it means

Error "Slack reactions.add failed ({status}): {sanitized}" thrown in zeroclaw-labs/zeroclaw.

Source

Thrown at crates/zeroclaw-channels/src/slack.rs:5508

            "channel": channel_id,
            "timestamp": ts,
            "name": name
        });

        let resp = self
            .http_client()
            .post("https://slack.com/api/reactions.add")
            .bearer_auth(&self.bot_token)
            .json(&body)
            .send()
            .await?;

        let status = resp.status();
        let text = resp.text().await.unwrap_or_default();

        if !status.is_success() {
            let sanitized = zeroclaw_providers::sanitize_api_error(&text);
            anyhow::bail!("Slack reactions.add failed ({status}): {sanitized}");
        }

        let parsed: serde_json::Value = serde_json::from_str(&text).unwrap_or_default();
        if parsed.get("ok") == Some(&serde_json::Value::Bool(false)) {
            let err = parsed
                .get("error")
                .and_then(|e| e.as_str())
                .unwrap_or("unknown");
            if err != "already_reacted" {
                anyhow::bail!("Slack reactions.add failed: {err}");
            }
        }

        Ok(())
    }

    async fn remove_reaction(
        &self,

View on GitHub (pinned to 88bb9c8533)

Solutions

1. Verify the bot token has reactions:write scope and the message timestamp/channel are correct; check the returned status.

When it happens

Trigger: Thrown at crates/zeroclaw-channels/src/slack.rs:5508 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of zeroclaw-labs/zeroclaw@88bb9c8533 (2026-08-23). Data as JSON: /api/errors/87ef91c06fb14a1c. Report an issue: GitHub.