Fivetran: Hybrid deployment syncs are delayed
Incident
Report for Fivetran
Resolved
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 <hd-agent-namespace> -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 <hd-agent-pod>
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 <hd-agent-namespace> -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 <hd-agent-pod>