tideflow. docs

Troubleshooting

Slack delivery failed

Check incoming webhook configuration, delivery logs, and common Slack notification failure points.

Last updated: 2026-04-06

Symptoms

You expected a Slack notification after a call was handled, but the message never arrived in your Slack channel.

First checks

  1. Check the delivery log — Go to Settings → Integrations and look at the delivery status for your Slack endpoint. Each delivery shows a status (delivered, pending, or failed), the HTTP response code, and an error message if something went wrong.
  2. Send a test notification— Use the test button in your Slack integration settings. If the test succeeds but real calls do not trigger notifications, check your event selection.
  3. Check the Slack channel— Confirm the webhook is pointed at the right channel and the channel still exists in Slack.

Common errors

HTTP 404 or 410

The webhook URL was deleted or the Slack app was removed. Generate a new incoming webhook URL in Slack and update it in your Tideflow integration settings.

HTTP 403

Your Slack workspace policy may be blocking the webhook, or the Slack app lost the permissions it needs. Check your Slack admin settings and verify the app still has access to the target channel.

HTTP 429

Slack is rate-limiting the webhook. Tideflow retries automatically with backoff. If this happens frequently, consider reducing the number of events you subscribe to or using a dedicated Slack channel with less traffic.

Timeout or network error

A temporary issue prevented the delivery. Tideflow retries failed deliveries up to three times with increasing delays (approximately one minute, then five minutes). If all retries fail, the delivery is marked as failed in the log.

Webhook URL requirements

Tideflow accepts Slack webhook URLs in these formats:

  • https://hooks.slack.com/services/...
  • https://hooks.slack-gov.com/services/... (GovSlack)

The URL must include three path segments after /services/. If your URL does not match this pattern, it will not be accepted.

Still not working

  • Verify the webhook URL was not rotated — if you regenerated the URL in Slack, the old one fails silently.
  • Try creating a new Slack app and incoming webhook to rule out app-level issues.
  • Contact support@tideflow.au with the delivery ID from your integration log so the team can investigate.

Next up

Webhook delivery issues→

Diagnose outbound webhook failures, receiver problems, and event delivery questions.