Slackbot
11/22/2025, 8:03 PMkapa.ai
11/22/2025, 8:03 PMFailure Origin: source vs Failure Origin: destination. - Any ConfigErrorException / schema validation errors / DB errors. - Example: a Postgres destination failure showed a config error on password type and was fixed by correcting connector settings in the UI and re‑checking the connector.[[Postgres to Postgres failing](https://discuss.airbyte.io/t/2348)] 2. If the destination (Postgres) is failing Common causes in the sources: - Bad or drifted destination config After upgrades or helm changes, the stored JSON config can become incompatible (wrong types, missing files). The fix is to open the destination in the UI, re‑enter credentials, and run “Check connection”; recreate the destination if needed.[[Postgres to Postgres failing](https://discuss.airbyte.io/t/2348); [MySQL over SSH -> Postgres](https://discuss.airbyte.io/t/1470)] - Temporary tables and disk usage When large syncs to Postgres fail, data may sit in _airbyte_tmp_* tables and consume storage until a successful job cleans them up.[[Source S3 space usage](https://discuss.airbyte.io/t/2067)] Remediation: - Connect to the destination DB. - List and manually drop _airbyte_tmp_* tables for that connection/schema. - Ensure you have enough free disk before re‑running. - Version/platform incompatibility Using a destination image that requires a newer platform will fail with messages like: You must upgrade your platform version to use this connector version. Either downgrade your connector or upgrade platform to 0.63.7.[[Dest Postgres platform version](https://github.com/airbytehq/airbyte/issues/54691)] On 0.63.2 you must: - Either upgrade the Airbyte platform to a compatible version (≥0.63.7 in that example), or - Use an older destination-postgres version that is supported by 0.63.2. 3. If the source (API via Connector Builder) is failing - For other sources, failed checks or syncs show messages like “Checking source connection failed – please review this connection’s configuration”.[[GA -> Postgres failed mode](https://discuss.airbyte.io/t/3628)] - For your custom API connector, follow the same pattern: - Open the source in the UI, verify all auth/URL/params, and run Check connection. - If config has changed in your API (auth, response shape, etc.), update the connector builder config accordingly. - If you recently upgraded the connector or platform, confirm the new schema is still valid (e.g., no JSON‑schema validation errors similar to those seen in other connectors).[[MySQL to Postgres failing](https://discuss.airbyte.io/t/3258)] 4. When to reset vs just re‑run - For CDC sources (e.g. Postgres) there are specific messages about invalid offsets and recommendations to reset the connection and then ensure WAL retention and sync frequency are sufficient.[[CDC invalid position](https://github.com/airbytehq/airbyte/issues/49802)] - For a custom API source (non‑CDC), resetting usually means: - From the connection page, click Reset connection to clear state. - Run a full resync to rebuild the destination data, then let regular incremental syncs resume. 5. General remediation loop For each failing connection: 1. Open the failing job and identify: - Failure origin (source/destination). - First clear error line (schema validation, config error, DB/network error). 2. Fix configuration at the failing side: - Re‑save connector settings, or recreate source/destination if config files may be missing or corrupted.[[MySQL over SSH -> Postgres](https://discuss.airbyte.io/t/1470)] 3. Clean up destination side effects if needed: - Drop _airbyte_tmp_* tables for large failed jobs.[[Source S3 space usage](https://discuss.airbyte.io/t/2067)] 4. Decide whether to: - Re‑run (for transient/network issues), or - Reset connection then run a fresh sync (for state/offset or schema drift issues).[[CDC invalid position](https://github.com/airbytehq/airbyte/issues/49802)] 5. Monitor logs for the next run to confirm it completes and tmp tables are cleaned automatically. The knowledge sources don’t include connector‑builder‑specific remediation steps beyond this general pattern; they also don’t document any special remediation workflow introduced in 0.63.2. If you can share the exact error from your failing job log (first “ERROR” with stack trace and failure origin), it would be possible to map it more precisely to one of the documented patterns above.kapa.ai
11/22/2025, 8:04 PMkapa.ai
11/22/2025, 8:05 PMkapa.ai
11/22/2025, 8:07 PMkapa.ai
11/22/2025, 8:08 PMjson { "data": { "workspace": { "id": "b510e39b-e9e2-4833-9a3a-963e51d35fb4", "name": "Workspace1", "url": "https://link/to/ws" }, "connection": { "id": "64d901a1-2520-4d91-93c8-9df438668ff0", "name": "Connection", "url": "https://link/to/connection" }, "source": { "id": "c0655b08-1511-4e72-b7da-24c5d54de532", "name": "Source", "url": "https://link/to/source" }, "destination": { "id": "5621c38f-8048-4abb-85ca-b34ff8d9a298", "name": "Destination", "url": "https://link/to/destination" }, "jobId": 9988, "startedAt": "2024-01-01T00:00:00Z", "finishedAt": "2024-01-01T01:00:00Z", "bytesEmitted": 1000, "bytesCommitted": 90, "recordsEmitted": 89, "recordsCommitted": 45, "errorMessage": "Something failed", "errorType": "config_error", "errorOrigin": "source", "bytesEmittedFormatted": "1000 B", "bytesCommittedFormatted": "90 B", "success": false, "durationInSeconds": 3600, "durationFormatted": "1 hours 0 min" } } [[Set up webhook notifications](https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/manage-airbyte-cloud-notifications#set-up-webhook-notifications)] Key fields you can use for alerting/automation: - success (false when failed) - errorMessage, errorType, errorOrigin - workspace, connection, jobId for routing to teams or dashboards. #### Successful sync payload Same structure, but without error fields and with success: true and fully committed bytes/records.[[Set up webhook notifications](https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/manage-airbyte-cloud-notifications#set-up-webhook-notifications)] #### Other events For some events (e.g., Connection Updates, Repeated Failures, Upgrade Required), the docs note: > “Webhook doesn’t contain payload and only works for Slack notifications.”[[Set up webhook notifications](https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/manage-airbyte-cloud-notifications#set-up-webhook-notifications)] So for those, your endpoint may just receive Slack‑formatted text blocks (and no data object). ### Using webhooks for monitoring/alerting in OSS In OSS, you typically: - Point the Webhook URL at: - A Slack Incoming Webhook (if you just want Slack alerts), or - Your own small service (or a generic gateway) that: - Parses the JSON payload, - Filters on success: false and specific connections, - Forwards to email/SMS/incident tools (PagerDuty, Opsgenie, etc.). This is the only built‑in alerting mechanism documented for OSS; there’s no native email for self‑managed instances, and the docs don’t show any additional OSS‑only alerting features beyond webhooks.