Fivetran incident

Fivetran: SQL Server TELEPORT and Epic CSA Connector POTENTIAL Failures Due to Unsupported Type in VIEW tables

Minor Resolved View vendor source →

Fivetran experienced a minor incident on April 2, 2026 affecting SQL Server and Epic Clarity, lasting 3h 37m. The incident has been resolved; the full update timeline is below.

Started
Apr 02, 2026, 05:45 PM UTC
Resolved
Apr 02, 2026, 09:22 PM UTC
Duration
3h 37m
Detected by Pingoru
Apr 02, 2026, 05:45 PM UTC

Affected components

SQL ServerEpic Clarity

Update timeline

  1. identified Apr 02, 2026, 05:45 PM UTC

    We identified a potential issue affecting the SQL Server (Teleport) and Epic CSA connectors, where syncs are failing with the following error. The action failed after 1 attempt(s), the failures were:1) java.lang.IllegalArgumentException: No enum constant com.fivetran.integrations.sql_server.connector.schema.SqlServerType.SYSNAME

  2. identified Apr 02, 2026, 06:37 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Apr 02, 2026, 09:03 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 02, 2026, 09:22 PM UTC

    This incident has been resolved. Incident Summary Description: We identified an issue affecting the SQL Server (Teleport) and Epic CSA connectors, where syncs were failing with the following error: java.lang.IllegalArgumentException: No enum constant com.fivetran.integrations.sql_server.connector.schema.SqlServerType.SYSNAME Timeline: The issue began on April 2, 2026, at 15:07 UTC and was resolved on April 2, 2026, at 20:49 UTC. Cause: A recent deployment introduced an issue impacting views in the Epic CSA and SQL Server (Teleport) connectors. Resolution: The deployment was rolled back, and a hotfix was applied, restoring normal operations.