@kapa.ai , i am google ads connector. After creating it it worked fine for the first time. Then i changed and put same query again using sdk option and now it is saying ‘GAQL’ is not subscriptable. Same query was working earlier and now its not. What should i do ?

Based on the information provided in the knowledge sources, it's not entirely clear why you're encountering the 'GAQL' is not subscriptable error. However, there are a few steps you can take to troubleshoot this issue: 1. Check your GAQL query: Make sure your GAQL query is correctly formatted. You can review the [Google Ads Query Language](https://developers.google.com/google-ads/api/docs/query/overview) and use the [query builder](https://developers.google.com/google-ads/api/fields/v17/query_validator) to validate your query. 2. Update your connector: If you're using an older version of the Google Ads connector, consider updating it. There was a [reported issue](https://github.com/airbytehq/airbyte/issues/32546) with custom GAQL queries that was fixed in version 3.1.0. 3. Recreate the source: According to a [forum post](https://discuss.airbyte.io/t/3756), a user was able to see their custom GAQL query after creating a new source from scratch. If none of these steps resolve your issue, I recommend reaching out to the Airbyte community on their [discussion forum](https://discuss.airbyte.io/) or opening a new issue on the [Airbyte GitHub page](https://github.com/airbytehq/airbyte/issues).

@kapa.ai this means i have to create a new gaql query every time if i customize gaql connection

A message from kapa.ai

No, you don't need to create a new GAQL query every time you customize the Google Ads connection. Once you've set up a custom GAQL query, you should be able to update or modify it as needed. However, if you're making changes to your custom GAQL queries, you should also refresh your source schema to pull in any changes. If you're adding new custom queries, you can do so in the Custom GAQL Queries field when setting up or editing your Google Ads source in Airbyte. You can add multiple queries if needed. Here's an example of a GAQL custom query:

sql SELECT       campaign.name,       metrics.conversions,       metrics.conversions_by_conversion_date   FROM ad_group

Remember to validate your queries using the [Google Ads Query Language guide](https://developers.google.com/google-ads/api/docs/query/overview) and the [query builder](https://developers.google.com/google-ads/api/fields/v17/query_validator). If you're encountering issues after updating your GAQL queries, it might be a good idea to check the [Airbyte discussion forum](https://discuss.airbyte.io/) or the [Airbyte GitHub issues](https://github.com/airbytehq/airbyte/issues) to see if others have experienced similar problems and how they resolved them.

@kapa.ai i am using sdk. Is there a special thing i need to do ?

A message from kapa.ai

When using the Airbyte SDK to develop a connector, there are a few key steps you need to follow: 1. Choose the right CDK: Airbyte provides two Connector Development Kits (CDKs) - one for Python and one for Java. The Python CDK is recommended for HTTP APIs, while the Java CDK is recommended for traditional databases. 2. Follow the development guide: Airbyte provides comprehensive guides for developing connectors using both the [Python CDK](https://docs.airbyte.com/connector-development/tutorials/building-a-python-source) and the [Java CDK](https://docs.airbyte.com/connector-development/tutorials/building-a-java-destination). These guides provide step-by-step instructions on how to develop, test, and publish your connector. 3. Stay updated: Developer updates are announced via the [#help-connector-development Slack channel](https://airbytehq.slack.com/archives/C027KKE4BCZ). If you are using the CDK, please join to stay up to date on changes and issues. 4. Follow best practices: Airbyte provides a list of [best practices](https://docs.airbyte.com/connector-development/best-practices) for developing and maintaining connectors. These include guidelines on error handling, testing, and performance optimization. 5. Ask for help: If you encounter any issues or have any questions, you can ask for help on the [#help-connector-development Slack channel](https://airbytehq.slack.com/archives/C027KKE4BCZ) or on the [Airbyte GitHub page](https://github.com/airbytehq/airbyte/issues). Remember, once a connector has been published for use within Airbyte, special care must be taken to account for the customer impact of updates to the connector.