Ben Karl

@ccapsuna yes, assuming you're using a `google-ads.yaml` file to configure the library, you can change the value [here](https://github.com/googleads/google-ads-python/blob/main/google-ads.yaml#L74) to `DEBUG` and get more detailed logs. Before you post those here,...

@ccapsuna I'm going to close this out since I can't reproduce it. Please post more details request/response logs when you can, if you're continuing to encounter this problem.

@yusuzech @ccapsuna thanks for all the details. After doing some research internally I learned that this behavior is expected, and that creating keyword plans via the API is currently in...

Hi All, sorry for the delayed response here, I was just checking whether you're still encountering these issues or not.

@ceijssen thank you, closing this for now but please add more details if this happens again.

@neeraj-sharma-nykaa assuming you've overcome this issue and closing this for now, please add more details if not and I'll be happy to help.

@sithara closing this for now assuming you were able to fix this issue on your own.

@mgallivan-loknow sorry for the delayed response. Can you share the full stack trace you're getting? Also how are you executing the example? Is it via a bash command line?

@karurb92 I'm having trouble reproducing this issue. Can you clarify what you have set for the [`use_proto_plus` ](https://github.com/googleads/google-ads-python/blob/main/google-ads.yaml#L18) configuration? And are you setting this configuration in multiple places? Also, are...

This actually works as intended if you have `use_proto_plus` set to `True`, for more details see [these docs](https://developers.google.com/google-ads/api/docs/client-libs/python/protobuf-messages#proto-plus_versus_protobuf_messages).