Google Ads Connector Issue with page_size Argument

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

The user is facing an issue with the Google Ads connector version 3.3.6 where the page_size argument is being flagged as invalid. The suggestion is to remove or modify the request object internally in the connector.


Question

Hi All,

We started facing issues in google ads connector from today (connector version 3.3.6)
as it is stating page_size is an invalid argument.
I guess, we may need to remove that argument / modify the request object internally in the connector only.
(<_InactiveRpcError of RPC that terminated with: status = StatusCode.INVALID_ARGUMENT details = "Request contains an invalid argument." debug_error_string = "UNKNOWN:Error received from peer ipv4:142.250.76.170:443 {created_time:"2024-08-23T01:34:42.395101391+00:00", grpc_status:3, grpc_message:"Request contains an invalid argument."}" >, <_InactiveRpcError of RPC that terminated with: status = StatusCode.INVALID_ARGUMENT details = "Request contains an invalid argument." debug_error_string = "UNKNOWN:Error received from peer ipv4:142.250.76.170:443 {created_time:"2024-08-23T01:34:42.395101391+00:00", grpc_status:3, grpc_message:"Request contains an invalid argument."}" >, errors { error_code { request_error: INVALID_PAGE_SIZE } message: "Page size is invalid." } request_id: "7K_BJPq9kI19ou7odxfJwA" , '7K_BJPq9kI19ou7odxfJwA')
Any help would be much appreciated
Thanks


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["google-ads-connector", "issue", "page-size", "invalid-argument"]
2

<@U0397RTD8E4>
If you can help on the same.
It will be really helpful

We are using this certified connector in our production pipeline
( i am also checking airbyte github , but that may take more time at my end )

3

What Airbyte version are you on?

4

Hi <@U05367G70MB>. Google Ads connector v3.7.0, published yesterday, resolves this issue. I recommend updating to the latest version!