@kapa.ai I tried to update connections settings cron expression, but got an unexpected error. Failed to update connection.

The knowledge sources don’t provide a specific root cause for a generic “Failed to update connection” error when changing a cron expression, but they do show a few common cron-related pitfalls and limits that can cause update failures. Here are the main things to check: 1. Validate the cron expression itself Airbyte uses Quartz-style cron, not standard UNIX cron. Make sure your expression follows Quartz rules (6 or 7 fields, with

?

in either day-of-month or day-of-week). [[Sync schedules](https://docs.airbyte.com/platform/using-airbyte/core-concepts/sync-schedules)] You can also use the Embedded API’s cron describe endpoint to validate and get a human-readable description:

http    POST /api/v1/integrations/templates/connections/cron/describe    Authorization: Bearer <token>    Content-Type: application/json     {      "cron_expression": "0 0 * * * ?"    }

[[Describe cron](https://docs.airbyte.com/ai-agents/embedded/api-reference/create-integrations-templates-connections-cron-describe)] 2. Respect minimum interval limits Airbyte Cloud does not allow syncs more frequent than every 60 minutes. If your cron expression results in runs closer than 1 hour apart, validation will fail (e.g., every 15 minutes). [[Sync schedules](https://docs.airbyte.com/platform/using-airbyte/core-concepts/sync-schedules); [Cron under 1h issue](https://github.com/airbytehq/airbyte/issues/51036)] 3. Watch out for known cron bugs in some OSS versions There is a reported bug in Airbyte 0.60 (OSS) where certain day-of-month values containing

0

(like

10

) cause “Invalid cron expression” even though the expression is valid, e.g.: - Works:

0 0 0 11,19,22 * ?

- Fails:

0 0 0 10,11,19,22 * ?

[[Cron day-of-month bug](https://github.com/airbytehq/airbyte/issues/54147)] If you’re on that version, this could be the reason your update fails when you change the cron. 4. General connection update failures There is also a report where a failed update on the backend led to a generic “Failed to update connection” message in the UI, even though the UI also showed “Your changes were saved!”. This indicates that when the backend rejects the update (e.g., due to invalid cron), the frontend may show a confusing generic error. [[Schema update error](https://github.com/airbytehq/airbyte/issues/57536)] --- Because the docs don’t show your exact cron expression or platform version, I can’t say precisely which of these is affecting you. To move forward: - Share the exact cron expression and your Airbyte deployment type/version. - Try validating the cron via the

/cron/describe

endpoint. - Ensure the schedule is at least 60 minutes apart (for Cloud). - If you’re on OSS 0.60 and using specific days of month with

0

(like

10

), this is likely the known bug; upgrading Airbyte (or at least the cron component, if feasible in your setup) is the documented workaround.