Refreshes do not trigger sync notifications

[kzvezdarov]

Topic

Refresh syncs do not trigger the execution of sync notifications, such as Successful Sync, Failed Sync

Relevant information

Platform Version

• Edition: community
• Version: Observed on 1.0.0, reproduced through 2.2
• Deployment: GKE, local abctl

Description

Triggering a Refresh Sync does not appear to execute any of the webhook notifications associated with sync events.

This is surprising because my impression from the documentation is that refresh syncs are considered to be syncs, and I'd expect to be able to notify on their success/failure (since they have similar effects - changes in the synced data).

The code in JobCreationAndStatusUpdateHelper.kt defines val SYNC_CONFIG_SET: Set<ConfigType> = setOf(ConfigType.SYNC, ConfigType.REFRESH), which seems in line with the documentation. The JobsHandler class though conditions sync notification execution on ConfigType.SYNC rather than SYNC_CONFIG_SET, meaning ConfigType.REFRESH do not emit notifications.

Steps to reproduce

1. Have a connection that supports Refresh Syncs
2. Configure and enable webhooks for Successful sync, Failed sync per https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/manage-airbyte-cloud-notifications#set-up-webhook-notifications
3. Sync the connection - observe notifications trigger.
4. Refresh the connections - no notifications trigger.

---

Internal Tracking: https://github.com/airbytehq/oncall/issues/13311

[octavia-bot]

AI Triage Starting...

Thank you for opening this issue! I'm an AI assistant that will do an initial review and may:

• Ask clarifying questions if needed
• Suggest relevant documentation or workarounds
• Flag this for internal visibility

Note: Community issues are reviewed on a best-effort basis and do not have a guaranteed response time. For additional help:

• Join the Airbyte Community Slack to connect with other users and community members
• If you're an Airbyte Cloud customer, you can open a support ticket or contact your account representative, referencing this issue URL

View playbook

• 🔗 Session URL: https://app.devin.ai/sessions/6eb4bd0652d443ae9c1755325091397c

✅ Devin AI session created successfully!

[airbyte-support-bot]

Hi Kiril Zvezdarov (@kzvezdarov), thank you for the detailed report and for including the code pointers and reproduction steps!

We've escalated this to our team for investigation: airbytehq/oncall#13311 (internal tracker).

One note for context: the notification and job-handling code you referenced lives in the airbytehq/airbyte-platform repository rather than this one, so any change would land there. We've kept the tracking on our side, so there's nothing further you need to do.

If you have anything else to add that would help the investigation, the most useful details would be:

• The exact platform version where you last reproduced this (you mentioned 2.2)
• Whether this also happens for a "Clear data" job, in addition to refreshes
• Whether it affects all notification channels you have configured (webhook, email, etc.)

If you share any logs, please mask or remove any sensitive information (API keys, passwords, tokens, connection strings) first.

---

Need more help? Join Airbyte Community Slack for peer support, or if you're a Cloud customer, open a support ticket referencing this URL.