Test, Monitor, and Retry Deliveries
Use delivery history to confirm Slack messages are rendered correctly, inspect Slack responses, and recover from failed deliveries.
The Slack integration includes delivery history for tests, subscribed contact events, and campaign workflow Slack actions. Use it to confirm messages are reaching Slack and to troubleshoot destination or template failures.
Send a destination test
Open Slack
Open Integrations, choose Slack, and stay on the Destinations tab.
Find the destination
Locate the destination you want to test.
Send test
Open the row action menu and choose Send test.
Review the delivery
Leadpush creates a slack.test delivery and opens it in the delivery detail view.
Confirm Slack
Check the Slack channel connected to the incoming webhook and confirm the message appears.
Send a workflow node test
The Send Slack campaign workflow node also includes a Send Test action. It sends a slack.test delivery using the selected destination and the current message templates in the node modal.
Use workflow node tests when you are validating text fallback and Block Kit formatting before saving or publishing the campaign workflow.
Delivery statuses
| Status | Meaning |
|---|---|
pending | The delivery was created and is waiting to be sent. |
processing | Leadpush is currently sending the delivery. |
retrying | The last attempt failed, and Leadpush will retry. |
succeeded | Slack returned a successful HTTP response. |
failed | Delivery attempts are exhausted or the delivery cannot be sent. |
Delivery detail
Open a delivery to review:
- event type and event id
- destination name
- rendered text fallback
- rendered Block Kit JSON
- Slack response status
- Slack response body excerpt
- error message
- attempt count
- next retry time
- individual attempt history
Leadpush stores response excerpts to help troubleshoot Slack failures without turning delivery history into a full payload archive.
Filter delivery history
Use filters to narrow delivery history by:
- destination
- event type
- delivery status
Common views include failed deliveries for a destination, all slack.test deliveries, all campaign.slack deliveries, or all deliveries for a specific contact event type.
Retry failed deliveries
Retry is available for failed deliveries.
Fix the issue
Resolve the underlying problem first, such as a disabled destination, replaced incoming webhook URL, invalid rendered blocks, or Slack rejecting the request.
Open the failed delivery
Open the delivery detail from the Delivery History tab.
Retry delivery
Click Retry Delivery.
Watch the status
Refresh or reopen the delivery to confirm it moves to pending, then succeeded or another failure state.
Common failure causes
| Symptom | What to check |
|---|---|
| Destination disabled | Enable the destination before retrying. |
| Slack returns an error | Incoming webhook URL, Slack app status, channel permissions, or message shape. |
| Rendered text is empty | Text fallback template and missing variables. |
| Rendered blocks are invalid | Block Kit JSON after variables are rendered. |
| Timeout | Destination timeout and Slack response latency. |
| No contact fields in test | slack.test does not include a contact payload. |
Production monitoring tips
- Send a test delivery after creating or editing a destination.
- Send another test after replacing an incoming webhook URL.
- Keep alert messages concise and high signal.
- Filter delivery history by
failedafter publishing new Slack subscriptions or campaign nodes. - Disable a destination before planned Slack app or channel maintenance if failures are expected.