Requested Improvement

Please introduce proactive notifications when an active table is automatically excluded due to:

• Permission or scope changes in the source system

• Connector configuration or authorization issues

• Any breaking change that stops data from syncing

Suggested Notification Options (one or more):

• Email notification to connector or account owners

• Optional webhook or alert integration

• Clear classification of warnings vs. breaking/critical events

• A short grace period or “pre-exclusion” warning before an active table is removed

Expected Benefit

This would allow customers to:

• React immediately to breaking changes

• Prevent data gaps in analytics and reporting

• Maintain confidence in Fivetran-managed production pipelines

This change would significantly improve reliability and operational trust for teams using Fivetran in production environments, especially for critical sources like Shopify.

Problem / Background

In multiple of our Shopify connectors, the customer table was automatically excluded from our Fivetran schema because the Shopify app temporarily lacked the write_customers permission. This exclusion happened without any proactive notification (email or alert), and the table stopped syncing silently. We only discovered the issue after BI consumers reported missing and incorrect data.

While Fivetran does surface warnings in the dashboard, these warnings are frequent and expected for many inactive or intentionally excluded tables. As a result, they are not sufficient for detecting critical, breaking changes affecting active tables in production schemas.

Why This Is an Issue

• An active, business-critical table was removed without notice.

• The lack of notification caused data inconsistencies in downstream BI and reporting.

• Silent failures undermine trust in data pipelines and require reactive firefighting instead of proactive mitigation.