A failed Mattermost delivery is logged as "slack notification failed" #227

New Issue

2026-10-02T07:35:33+02:00

clawbot commented

2026-10-02 07:35:33 +02:00

Found in the trial run for #149.

When the Mattermost endpoint answered with an HTTP error, the warning said "endpoint":"mattermost" but "error":"slack notification failed: status 503". Mattermost notifications are sent by the Slack sender, so the error names Slack; ErrMattermostFailed in internal/notify/notify.go is defined and never used. With both endpoints set, the error reads as a Slack failure.

To see it, point DNSWATCHER_MATTERMOST_WEBHOOK at a URL that answers 503 and read the retry warning. The Mattermost sender is set up in dispatchMattermost in internal/notify/notify.go.

Definition of done

A failed Mattermost delivery's error names Mattermost, and a failed Slack delivery's error names Slack.
A delivery test with a stand-in endpoint checks the Mattermost error.

Model: opus-5-5

Found in the trial run for https://git.eeqj.de/sneak/dnswatcher/issues/149. When the Mattermost endpoint answered with an HTTP error, the warning said `"endpoint":"mattermost"` but `"error":"slack notification failed: status 503"`. Mattermost notifications are sent by the Slack sender, so the error names Slack; `ErrMattermostFailed` in `internal/notify/notify.go` is defined and never used. With both endpoints set, the error reads as a Slack failure. To see it, point `DNSWATCHER_MATTERMOST_WEBHOOK` at a URL that answers 503 and read the retry warning. The Mattermost sender is set up in `dispatchMattermost` in `internal/notify/notify.go`. ## Definition of done - A failed Mattermost delivery's error names Mattermost, and a failed Slack delivery's error names Slack. - A delivery test with a stand-in endpoint checks the Mattermost error. Model: opus-5-5

clawbot added this to the 1.0 milestone 2026-10-02 07:35:33 +02:00

clawbot referenced this issue

2026-10-02 07:35:45 +02:00

Trial run of the finished image against real targets before tagging 1.0 #149

clawbot referenced this issue

2026-10-02 07:39:18 +02:00

Review toward 1.0: identify and file all next steps #144

clawbot referenced this issue from a commit

2026-10-02 08:14:47 +02:00

notify: a failed Mattermost delivery's error names Mattermost (closes #227)

clawbot referenced a pull request that will close this issue

2026-10-02 08:15:01 +02:00

notify: a failed Mattermost delivery's error names Mattermost #240

clawbot commented

2026-10-02 08:15:11 +02:00

Built in #240: the Slack sender now wraps an HTTP error in the error of the endpoint it is sending for, so a failed Mattermost delivery reads mattermost notification failed.

Model: opus-5-5

Built in https://git.eeqj.de/sneak/dnswatcher/pulls/240: the Slack sender now wraps an HTTP error in the error of the endpoint it is sending for, so a failed Mattermost delivery reads `mattermost notification failed`. Model: opus-5-5

clawbot referenced this issue from a commit

2026-10-02 08:39:39 +02:00

notify: a failed Mattermost delivery's error names Mattermost (closes #227)

clawbot closed this issue

2026-10-02 08:40:20 +02:00

clawbot referenced this issue from a commit

2026-10-02 08:40:20 +02:00

notify: a failed Mattermost delivery's error names Mattermost (closes #227)

Sign in to join this conversation.