@kapa.ai google ads getting error 'Stream customer is not available: HTTP Status Code: 400. Error: Bad request. Please check your request parameters.'

Google Ads "Stream customer" HTTP 400 Error This error typically occurs when the Google Ads connector sends an invalid or unsupported query to the Google Ads API. Based on the knowledge sources, here are the most likely causes and what to check: Common Causes 1. Invalid custom GAQL query fields If you have configured custom GAQL queries, they may reference field names that are no longer valid in the current API version (e.g., fields from Google Ads API v20 that were removed in v23). [fix PR 78419] 2. Prohibited metrics in SELECT clause A custom query may be selecting a metric that is not allowed for the queried resource (e.g.,

PROHIBITED_METRIC_IN_SELECT_OR_WHERE_CLAUSE

). [fix PR 78384] 3. Unrecognized field names Custom queries referencing fields that don't exist for the queried resource will be rejected with a 400 error. The connector's error handling in

utils.py

surfaces this as: "Custom query references an unrecognized field for the queried resource. Verify all selected fields are valid for the resource." [utils.py] Steps to Resolve 1. Review your custom GAQL queries — If you have any custom queries configured, check that all field names are valid for the Google Ads API v23. You can validate fields using the Google Ads API field reference. 2. Check for prohibited metrics — Some metrics cannot be selected alongside certain resources. Remove any metrics that are not supported for the

customer

resource. 3. Update your connector version — Older versions (e.g., 3.x) had issues with customer ID filtering and query construction. Upgrading to a recent version (4.2.7+ or 5.x) includes improved error classification that will surface a clearer

config_error

message instead of a generic bad request. [fix PR 78384] 4. Verify customer account status — Ensure the customer account is active and not deactivated. A deactivated or not-yet-enabled account can also cause request failures. [utils.py] Note on Recent Fixes Recent connector versions added better error classification for 400 responses from invalid GAQL queries, so upgrading should give you a more descriptive error message pointing to the exact problem. However, note that version 5.0.1 introduced a response filter that could cause OOM issues on large streams, which was subsequently removed in 5.0.2. [fix PR 78514] If you share the full error details or your custom query configuration, I can help narrow down the cause further. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai 2026-07-28 122249 info Connector exited, processing output 2026-07-28 122249 info Output file jobOutput.json found 2026-07-28 122249 info Connector exited with exit code 0 2026-07-28 122249 info Reading messages from protocol version 0.2.0 2026-07-28 122249 error 'GET' request to 'googleads.googleapis.com/v20/customers:listAccessibleCustomers' failed with status code '400' and error message: 'Request contains an invalid argument.'. Request (body): 'None'. Response (body): '{'error': {'code': 400, 'message': 'Request contains an invalid argument.', 'status': 'INVALID_ARGUMENT', 'details': [{'@type': 'type.googleapis.com/google.ads.googleads.v20.errors.GoogleAdsFailure', 'errors': [{'errorCode': {'requestError': 'UNSUPPORTED_VERSION'}, 'message': 'Version v20 is deprecated. Requests to this version will be blocked.'}], 'requestId': 'Vx5NLA6WvSNxcivJ6SO9FQ'}]}}'. Response (headers): '{'Request-Id': 'Vx5NLA6WvSNxcivJ6SO9FQ', 'Vary': 'Origin, X-Origin, Referer', 'Content-Type': 'application/json; charset=UTF-8', 'Content-Encoding': 'gzip', 'Date': 'Tue, 28 Jul 2026 162248 GMT', 'Server': 'ESF', 'X-XSS-Protection': '0', 'X-Frame-Options': 'SAMEORIGIN', 'X-Content-Type-Options': 'nosniff', 'Transfer-Encoding': 'chunked'}'. 2026-07-28 122249 warn Stream customer is not available: HTTP Status Code: 400. Error: Bad request. Please check your request parameters. 2026-07-28 122249 error Check failed 2026-07-28 122249 info Checking for optional control message... 2026-07-28 122249 info Optional control message not found. Skipping... 2026-07-28 122249 info Writing output of 253487c0-2246-43ba-a21f-5116b20a2c50_072fdf21-03e0-43cb-901a-49beea0eedb1_0_check to the doc store 2026-07-28 122249 info Marking workload 253487c0-2246-43ba-a21f-5116b20a2c50_072fdf21-03e0-43cb-901a-49beea0eedb1_0_check as successful 2026-07-28 122249 info 2026-07-28 122249 info Deliberately exiting process with code 0. 2026-07-28 122249 info ----- END CHECK ----- 2026-07-28 122249 info

Root Cause: Google Ads API v20 Deprecated Your logs make the cause very clear:

'errorCode': {'requestError': 'UNSUPPORTED_VERSION'},
'message': 'Version v20 is deprecated. Requests to this version will be blocked.'

Your connector is calling

googleads.googleapis.com/v20/...

but Google Ads API v20 has been sunset as of today (July 28, 2026). What's Happening Looking at the Airbyte connector release history, version 4.0.0 upgraded the connector to use Google Ads API v20. A subsequent 5.0.0 release was planned to upgrade to v23, but that release was reverted back to 4.2.6 (v20) in a recent PR. [revert PR] This means the current connector on

master

is still pointing at v20, which Google has now deprecated. [metadata.yaml] What You Should Do 1. Check if a newer connector version is available in your Airbyte instance. The

metadata.yaml

shows a

4.0.0

breaking change entry referencing an upgrade to v20 with an

upgradeDeadline

of

2025-08-19

, and a

5.0.0

entry upgrading to v23. [metadata.yaml] 2. If you are on Airbyte Cloud, this is a known issue with the connector — the v20→v23 upgrade (version 5.0.0) was reverted and needs to be re-released. You should contact Airbyte support or watch for a new connector release. 3. If you are on Airbyte OSS/self-managed, you may need to wait for Airbyte to publish a new connector version that targets Google Ads API v23 or later. > ⚠️ The knowledge sources do not contain enough information to confirm whether a fixed connector version has been published after the revert. I'd recommend checking the Airbyte connector registry or the GitHub issue tracker for the latest status on the Google Ads API v23 upgrade. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai any issue from google ads side or issue in airbyte

It's an Airbyte Connector Issue Based on the logs and knowledge sources, the problem is on Airbyte's side, not Google's. Here's why: • Google's deprecation of v20 is expected and announced — Google communicated the v20 sunset well in advance (deadline was August 20, 2025). [metadata.yaml] • Airbyte did build a fix — Version 5.0.0 of the connector upgraded the Google Ads API from v20 to v23, which would have resolved this. [migration guide] • But Airbyte reverted that fix — PR #78502 rolled the connector back to version 4.2.6 (API v20), meaning the connector is now calling a deprecated API endpoint. [revert PR] So in summary: The knowledge sources do not explain why the 5.0.0 release was reverted, so I cannot confirm the exact reason. I'd recommend raising this directly with Airbyte support or monitoring the GitHub repository for a new connector release that targets Google Ads API v23 or later. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements

Sorry @Srikar Chamarthy, I'm not sure what you mean. Please try again. 👋

@kapa.ai 'GET' request to 'googleads.googleapis.com/v20/customers:listAccessibleCustomers' failed with status code '400' and error message: 'Request contains an invalid argument.'. Request (body): 'None'. Response (body): '{'error': {'code': 400, 'message': 'Request contains an invalid argument.', 'status': 'INVALID_ARGUMENT', 'details': [{'@type': 'type.googleapis.com/google.ads.googleads.v20.errors.GoogleAdsFailure', 'errors': [{'errorCode': {'requestError': 'UNSUPPORTED_VERSION'}, 'message': 'Version v20 is deprecated. Requests to this version will be blocked.'}], 'requestId': '1XVef07TPSauCqX5XIQ5ow'}]}}'. Response (headers): '{'Request-Id': '1XVef07TPSauCqX5XIQ5ow', 'Vary': 'Origin, X-Origin, Referer', 'Content-Type': 'application/json; charset=UTF-8', 'Content-Encoding': 'gzip', 'Date': 'Tue, 28 Jul 2026 174050 GMT', 'Server': 'ESF', 'X-XSS-Protection': '0', 'X-Frame-Options': 'SAMEORIGIN', 'X-Content-Type-Options': 'nosniff', 'Transfer-Encoding': 'chunked'}'.

This is the same issue we identified previously — Airbyte's Google Ads connector is still calling the deprecated v20 API endpoint, which Google is now blocking. Current Situation The knowledge sources confirm: • Airbyte did release connector version 5.0.0 upgrading to Google Ads API v23 [migration guide] • That release was reverted back to v20 (4.2.6) via PR #78502 • The v20 sunset deadline was August 19, 2025 [metadata.yaml] What You Can Do Right Now 1. Contact Airbyte Support — Report this as an urgent production issue since the connector is completely broken for all users on the current version. 2. Monitor the Airbyte GitHub — Watch for a new connector release targeting Google Ads API v23 or later at the source-google-ads connector. 3. If on Airbyte Cloud — Check if a newer connector version (5.x) has been re-released and is available to upgrade to in your workspace. > ⚠️ The knowledge sources do not contain information about a re-release of the v23 upgrade after the revert, so I cannot confirm whether a working version is currently available. Reaching out to Airbyte support directly is the most reliable path forward. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.