The knowledge sources don’t contain a direct description of the exact error message you’re seeing for the Google Ads “Test” save action, but they do show closely related issues and how Airbyte surfaces HTTP errors. 1. What

errors.http.default

means In other contexts, Airbyte surfaces HTTP errors as a generic

errors.http.default

with an attached HTTP status code and backend message (for example, a 409 with “Failed to access database. Check the server logs for more information”). [[DB 409 issue](https://github.com/airbytehq/airbyte/issues/54150)] This suggests your “Failed to save Google Ads Test due to the following error: errors.http.default” is a generic UI wrapper around an HTTP error returned by the Airbyte backend (not by Google Ads itself). 2. Known Google Ads–related save/check issues - There is an open issue where a Google Ads source “Check connection” passes at the connector level but the platform fails with

422 Unprocessable Entity

on an internal

updateSource

call after the check, even though the same config works on Airbyte Cloud. [[Google Ads 422 issue](https://github.com/airbytehq/airbyte/issues/60900)] - Another open issue reports Google Ads authentication problems that appear specific to Airbyte’s handling of Google Ads credentials, while the same credentials work in another tool. [[Google Ads auth issue](https://github.com/airbytehq/airbyte/issues/63374)] Your symptom (“Failed to save … Test”) is consistent with these platform‑side problems: the connector may be fine, but the platform fails when persisting or updating the source. 3. What you can do next Because the sources don’t show a definitive fix for your exact message, I can’t say precisely what’s wrong in your instance. However, based on the related issues, the next concrete steps are: - Check the underlying HTTP error and logs - Look at the browser network tab for the failing request (likely

/api/v1/sources/create

or

/api/v1/sources/update

or

updateSource

) and note the HTTP status code and response body. - Check

airbyte-server

logs around the time of the failure; in similar cases they contain a more specific message (e.g., DB conflict, validation error). [[DB 409 issue](https://github.com/airbytehq/airbyte/issues/54150); [Google Ads 422 issue](https://github.com/airbytehq/airbyte/issues/60900)] - Compare with the known 422 Google Ads issue If you see a

422 Unprocessable Entity

on an internal

updateSource

call after a successful check, you’re likely hitting the same bug as in the OSS +

abctl

deployment report. [[Google Ads 422 issue](https://github.com/airbytehq/airbyte/issues/60900)] In that case, the problem is on the platform side rather than your Google Ads credentials. - Try on Airbyte Cloud or another environment (if possible) In the 422 issue, the same Google Ads config worked on Airbyte Cloud but failed on a specific OSS deployment, which helped confirm it was a platform bug. [[Google Ads 422 issue](https://github.com/airbytehq/airbyte/issues/60900)] If you can share the HTTP status code and response body from the failing request (or the corresponding

airbyte-server

log line), I can help you map it more precisely to the known issues in the provided sources.