Hi everyone! We have been using Facebook Marketing connector and today we started getting the following error:

(#100) Tried accessing nonexisting field (cost_per_conversion_lead) on node type (AdsInsights)

and the strange thing is cost_per_conversion_lead is not even checked in the connection. Anyone knows why we get an error for a field we are not pulling? It seems like the connector needs an urgent update...

It seems like you are encountering an issue with the Facebook Marketing connector related to an invalid field

cost_per_conversion_lead

. This type of error can occur if the connector is not fully compatible with the latest version of the Facebook API or if there are discrepancies in the fields being requested. Here are a few steps you can take to address this issue: 1. Update the Connector: Ensure that you are using the latest version of the Facebook Marketing connector. Sometimes, updating to the latest version can resolve issues related to field compatibility. For example, in [Issue #35920](https://github.com/airbytehq/airbyte/issues/35920), a similar problem was resolved by updating to a version compatible with the latest API. 2. Check for Known Issues: Review recent issues reported on the Airbyte GitHub repository to see if others are experiencing similar problems. For instance, [Issue #38154](https://github.com/airbytehq/airbyte/issues/38154) discusses data mismatches and errors with specific fields, which might be related to your issue. 3. Report the Issue: If updating the connector does not resolve the problem, consider reporting the issue on the Airbyte GitHub repository. Provide as much detail as possible, including the connector version, the specific error message, and any relevant configuration details. This will help the Airbyte team and community members to diagnose and address the issue more effectively. 4. Review Connector Configuration: Double-check your connector configuration to ensure that no deprecated or invalid fields are being requested. Even if

cost_per_conversion_lead

is not explicitly checked, there might be other configurations or default settings causing the issue. If you need further assistance, you can refer to the following issues for more context and potential solutions: - [Issue #35920](https://github.com/airbytehq/airbyte/issues/35920) - [Issue #38154](https://github.com/airbytehq/airbyte/issues/38154) If none of these steps resolve your issue, you might need to wait for an official update from the Airbyte team or contribute to the connector's improvement by providing detailed feedback. For more detailed documentation, you can visit the [Airbyte documentation](https://docs.airbyte.com/). I hope this helps! If you have any more questions or need further assistance, feel free to ask.