Use a test message after connecting Slack or changing workspace settings. Delivery history then helps distinguish an Uptime Basics event-filter issue from a Slack delivery problem.
Send a test
- Open Integrations.
- Find the Slack connection.
- Select Send test.
- Wait briefly and confirm the message appears in the selected channel.
- Select History to review the recorded attempt.
A test message is clearly identified as a test. It does not create an incident, change a monitor, or notify other account alert channels. It does count toward the monthly integration delivery allowance.
Read connection health
- Connected - awaiting first delivery: The authorization is saved, but no successful delivery is recorded yet.
- Connected: The most recent delivery health is normal.
- Needs attention: Recent attempts failed and should be reviewed.
- Paused: Delivery is off until you enable it.
- Delivery suspended: Repeated failures stopped delivery to prevent an endless retry loop.
- Reconnect required: Slack no longer accepts the saved destination credential.
The connection card shows the most recent successful delivery and, when applicable, the most recent failed delivery.
Review delivery history
History shows a bounded recent list with:
- Event type and delivery time.
- Delivered or failed state.
- HTTP response status when available.
- Delivery duration.
- A safe failure category or concise explanation.
Uptime Basics does not display or retain Slack response bodies or the Slack destination credential.
Redeliver a failed event
When retained event data is available, a failed history entry includes Redeliver. Redelivery creates a new delivery attempt for the same event. Use it after correcting the connection, and avoid repeatedly pressing it while an attempt is pending.
Manual redeliveries count toward the monthly allowance. Some older records may not include the safe event data required for redelivery.