Error Starting Manual Syncs or Historical Re-syncs with Connections

This incident has been resolved. We have observed that sync and re-sync actions are working as expected and no additional warnings have been found.

Incident Summary
Description:
Manual sync or re-sync requests via the Dashboard or API returned an error.
The following error is returned by the Dashboard:
"Failed to update integration. If this continues to occur, please contact support."

Timeline:
The incident began on 2025-10-10 at 18:16 UTC and was resolved on 2025-10-10 at 21:36 UTC.

Cause:
Scheduling configuration was stored in unexpected format, this caused a failure when manual sync operation tried to identify whether the connector has dependent transformations.

Resolution:
A hotfix was deployed to cover additional cases of the scheduling configuration format.

The hotfix is now live, and manual syncs/re-syncs through the Dashboard and API are working as expected.

We are continuing to monitor all affected connectors after the recent fix deployment.

We have deployed a hotfix for this issue: Integrated scheduling is not outputting expected results, causing downstream queries which manual sync/re-sync operations depend on to fail.

Once the hotfix has gone live, we will continue to monitor all affected connectors until they resume their normal sync functionality.

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

Beginning at 18:16 UTC, manual sync or re-sync requests via the Dashboard or API started to return an error.

The following error is returned by the Dashboard:
"Failed to update integration. If this continues to occur, please contact support."

The following error is returned by the API:
"[SQL State: 22023] ERROR: cannot extract elements from a scalar"