@kapa.ai The overnight connections run and sync successfully, but the notifications do not fire. Any thoughts on why? Where should I start troubleshooting from?

Based on the docs and issues, there are a few concrete things you can check. 1. Confirm the notification type is actually enabled Notifications are configured per workspace and per event type. Make sure, in Workspace settings → Notifications, that: • The relevant event types (e.g. Successful syncs, Failed syncs) are toggled on for: ◦ Email (if using Cloud email), and/or ◦ Webhook (if using webhooks). [Manage notifications] If you expect schema‑change notifications, also ensure Connection Updates and Connection Updates Requiring Action are enabled; otherwise schema notifications won’t be sent even if enabled on the connection itself. [Manage notifications] 2. Verify you’re using an event that actually sends a webhook payload For webhooks, only Failed syncs and Successful syncs send a JSON payload. Other events like “Connection updates”, “Warning – Repeated Failures”, etc. are Slack‑only and “don’t contain payload and only work for Slack notifications.” [Webhook payloads] So if you configured a webhook for, say, “Connection updates”, you won’t see any webhook calls. 3. Check that the sync is truly classified as “successful” or “failed” There is at least one reported case where a MySQL sync finished with a green “successful” status but didn’t move data and did not trigger either “Successful syncs” or “Failed syncs” notifications, suggesting some edge cases where the job status doesn’t map cleanly to those events. [MySQL success but no notification] If your runs show unusual metrics (e.g., 0 records, or partial success), this might be similar. 4. Validate webhook configuration itself For webhook notifications: • Use the Test button in the Notifications UI to confirm Airbyte can reach your webhook URL. • Ensure the URL is accepted for the specific event type. There was a Cloud bug where “Successful syncs” webhook URLs were rejected/invalid while other events worked; this was later fixed. [Webhook bug] If tests succeed but real runs don’t trigger anything, it’s more likely an event‑type or job‑status issue than connectivity. 5. Distinguish Cloud vs self‑managed behavior • Cloud: can send email and webhook. [Manage notifications] • Self‑managed: only webhook, no email. [Manage notifications] Make sure you’re looking at the right column (Email vs Webhook) for your deployment. If after checking: 1. The correct event types are enabled, 2. You’re using Failed/Successful syncs for webhooks, 3. Test notifications work, but real syncs still don’t fire notifications, then the knowledge sources don’t provide more specific troubleshooting steps. In that case, capturing a recent job run (with its status and metrics) and opening a GitHub issue or support ticket with those details would be the next step. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.