<@U04S8PLJWMT> getting error with google ads 'Stre...
# replication-ask-ai
s
@kapa.ai getting error with google ads 'Stream customer is not available: HTTP Status Code: 400. Error: Bad request. Please check your request parameters.'
k
Google Ads "Stream customer" HTTP 400 Error This error typically occurs when the Google Ads connector sends an invalid query or request to the API. Based on the knowledge sources, here are the most likely causes and what to check: Common Causes 1. Invalid Custom GAQL Query If you have configured a custom GAQL query, it may contain:[PR #78384] [PR #78419] ◦ Fields that are not valid for the queried resource (
PROHIBITED_METRIC_IN_SELECT_OR_WHERE_CLAUSE
) ◦ Unrecognized field names (e.g., fields from an older API version like v20 that are no longer valid in v23) 1. Incorrect Request Parameters The
customer
stream maps to the
customer
resource in Google Ads. A 400 response means the API rejected the request as invalid. What to Try • Check your custom queries: If you have any custom GAQL queries configured, verify that all selected fields are valid for the resource you are querying against the current Google Ads API (v23). • Update the connector: Two recent fixes (versions
4.2.7
and
5.0.1
) specifically address HTTP 400 errors from invalid custom GAQL queries, classifying them as configuration errors with clearer messages. Make sure you are on the latest version of the Source Google Ads connector. [PR #78384] [PR #78419] • Check customer account status: The connector also handles cases where a customer account is not enabled or has been deactivated. Verify your Google Ads customer account is active. [streams.py] • Verify credentials and permissions: Ensure your developer token, client ID/secret, and refresh token are all valid and that the account has the necessary permissions. Error Classification After Fix After upgrading to the latest connector version, invalid custom query errors should surface as configuration errors with a specific message indicating which field or condition was rejected, rather than a generic bad-request failure. [PR #78384] If you are still seeing this error after checking the above, please share your custom GAQL query (if any) and the exact connector version you are using for further diagnosis. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
s
@kapa.ai i have not added any custom queries
k
I'm sorry, but the knowledge sources do not contain enough specific information to definitively diagnose a HTTP 400 error on the
customer
stream when no custom queries are involved. However, based on what is available, here are the most relevant things to check: 1. Re-authenticate Your Credentials Expired or revoked OAuth credentials can cause unexpected errors. Try re-authenticating your connection by editing your source and updating your credentials. [GitHub Issue] 2. Check Your Customer ID Configuration • Ensure the Customer ID entered in the connector configuration is correct and that your credentials have access to it. • If your account is under a manager (MCC) account, make sure the
login_customer_id
is set to the manager account ID. [GitHub Issue] 3. Verify Account Status Make sure the Google Ads customer account is active and has completed signup — deactivated or incomplete accounts will cause request failures. [streams.py] 4. Check Permissions Ensure the authenticated user has sufficient permissions to access the customer account. A
USER_PERMISSION_DENIED
or
CUSTOMER_NOT_FOUND
error from Google Ads can sometimes surface as a generic 400. [utils.py] If none of these resolve the issue, I'd recommend opening a support ticket with Airbyte and sharing the full sync logs for further investigation. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
s
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