Start with the connection card and delivery history. A healthy website monitor can still have a Slack configuration or delivery problem, and a healthy Slack connection does not change how an outage is confirmed.
A monitoring event did not appear
- Confirm the Slack connection is Connected and not paused.
- Open Configure and confirm the event type is selected.
- If the connection uses Selected monitors, confirm the affected monitor is selected.
- Confirm the monitor feature exists and is enabled. For example, selecting an SSL event does not enable SSL monitoring.
- Review History for a matching failed attempt.
- Send a test message.
An availability notification is sent only after the monitoring system confirms the state change. Temporary failures that never become a confirmed incident do not produce an incident-opened message.
A test is queued but does not arrive
- Wait briefly and reopen History.
- Confirm you are viewing the same workspace and channel shown on the connection card.
- Check whether the Slack app or incoming webhook was removed by a workspace administrator.
- Check whether the destination channel was archived or removed.
- Review workspace policies that may prohibit incoming webhooks.
Delivery is suspended
Repeated failures can suspend a connection to prevent an endless delivery loop. Correct the Slack destination or workspace policy, select Enable, and send a test. A successful attempt resets the consecutive-failure state.
Reconnect is required
The saved Slack destination is no longer authorized or active. Select Reconnect, approve the intended channel again, and send a test. A reconnect-required connection cannot be enabled without completing authorization.
Rate limiting or temporary provider errors
Temporary provider failures are retried through the delivery queue with bounded delays. Slack rate-limit instructions are respected within the queue's maximum delay. Do not repeatedly send tests while a temporary failure is already retrying.
Monthly allowance reached
The Integrations page shows delivery usage and the plan allowance. Tests, retries, generic webhook attempts, and Slack attempts share this total. Delivery resumes when the UTC monthly allowance resets or when account limits change.
Information to include in a support request
Include:
- Connection display name.
- Workspace and channel shown on the card.
- Approximate event and test times, including time zone.
- Monitor name and expected event type.
- Customer-visible health state and safe failure category.
Do not send Slack webhook URLs, authorization codes, account passwords, API tokens, or monitor authentication values.