Consequent manually triggering sync via API or in the UI is throwing an error if the connector is still running.

Incident Report for Fivetran

Resolved

Incident Summary

Description:
Consequent manually triggering sync via API or in the UI is throwing an error if the connector is still running and it also was started with the API call or from the UI.

Timeline:
July, 24 at 10:00 UTC until July, 29 at 14:00 UTC

Cause:
The issue was with the consequent sync triggers that caused the syncs to fail.

Resolution:
The issue has been fully resolved, and all affected services have returned to normal functionality.

Posted Jul 29, 2025 - 10:00 UTC