Fivetran incident

Fivetran: Hybrid deployment syncs are delayed

Notice Resolved View vendor source →

Fivetran experienced a notice incident on April 16, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Apr 16, 2026, 06:00 PM UTC
Resolved
Apr 16, 2026, 06:00 PM UTC
Duration
—
Detected by Pingoru
Apr 16, 2026, 06:00 PM UTC

Update timeline

  1. resolved Apr 17, 2026, 12:58 AM UTC

    This incident has been resolved. Incident Summary Description: We identified an issue where connectors using the Hybrid Deployment agent were unable to schedule new sync jobs. Timeline: This issue began on 2026-04-15 18:30 UTC and was resolved at 2026-04-16 23:20 UTC. Cause: The issue was caused by a recent code change. Resolution: The changes have been reverted, and the HD Agents affected will require a restart. During the restart, the latest update will be automatically applied, resolving the issue and preventing recurrence. Steps to restart your agent: For Docker and Podman deployments: ./hdagent.sh stop ./hdagent.sh start For Kubernetes deployments: 1. Get the HD Agent pod: kubectl get pod -n -l app.kubernetes.io/name=hd-agent 2. Kill the pod, which will force it to restart and pull the latest image kubectl delete pod