Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Notification for Automatic Connector Pause After 14 Days of Sync Failures

Answered
Sujith Kumar Somisetti User

We request a feature enhancement to send a clear notification when a connector is automatically paused by Fivetran after repeated sync failures for 14 days.

Currently, failure notifications are sent while retries are happening, but there is no separate alert when the connector is ultimately auto-paused. This creates a risk for production pipelines, because teams may miss the final state change and only discover the issue later after data stops flowing.

Requested enhancement:

  • Send a dedicated notification when a connector is automatically paused by the system.
  • Include key details such as:
    • Connector name
    • Destination / schema
    • Time and date of auto-pause
    • Reason for auto-pause
    • Duration of failure period
    • Link to connector/dashboard for quick action
  • Support notifications through existing channels such as email, webhook, Slack, or other configured alerting mechanisms.
  • Optionally provide admin-level and account-level alerts for critical production connectors.

Business impact:

  • Prevents unnoticed data pipeline stoppages
  • Improves operational visibility for production systems
  • Reduces time to detect and resolve issues
  • Helps teams take immediate action before downstream reporting or business processes are affected

This feature would significantly improve monitoring and reliability for customers running critical production workloads on Fivetran.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Amy Peterson Fivetranner

    Hi Sujith,

    Thanks for the detailed request! Fivetran does fire an event when a connector is auto-paused after 14 days of sync failures. When the auto-pause triggers, a pause_connector event is fired and flows through to the Fivetran Platform Connector. In your log table, you'll see:

    • message_event = "pause_connector"
    • message_data containing a reason field set to "Connection is paused due to an unresolved error" This means you can use the Platform Connector logs to detect and alert on auto-pauses today — for example, by querying for pause_connector events where the reason indicates an unresolved error, and piping that into your preferred alerting tool (webhook, Slack, etc.). That said, we hear you on wanting a more out-of-the-box, purpose-built alert for this specific scenario without needing to build a custom query. We'll keep this open to track interest in a dedicated notification experience for auto-pauses. 

    Thanks,

    Amy

  • Henry Dodge Fivetranner
    • Edited

    Hi Sujith,

    Thank you for submitting this request! We are in the process of triaging it with the appropriate team members and will get back to you soon.

    Thanks,

    Henry