Hey everyone, I'm building a Podio source connect...
# help-connector-development
j
Hey everyone, I'm building a Podio source connector and using BigQuery as the destination. I'm currently retrieving data from 20 Podio apps, and all but 1 of the apps get successfully uploaded to BigQuery. The one app that fails gives me these errors:
Copy code
"Pickling client objects is explicitly not supported. Clients have non-trivial state that is local and unpickleable."
Copy code
"Failure Origin: normalization, Message: Normalization failed during the dbt run. This may indicate a problem with the data itself."
I can't figure out why that 1 app fails, as I don't see any difference between this app and the rest of them. The data gets retrieved successfully from this app, and as far as I figure something is happening on the BigQuery connector end. Any lead would be appreciated, thank you 🙏
k
A message from kapa.ai
Hmm, I don't know enough to give you a confident answer yet. However, I can provide some general suggestions based on the information extracts. 1. Check the logs for more details about the error. You can find logs in the Airbyte UI or, if you're using Kubernetes, you can check the logs in your Kubernetes deployment. This might give you more insights into what's causing the issue. 2. Make sure you're using the latest version of the Airbyte and the connectors. Sometimes, issues are resolved in newer versions. 3. Try running the sync again, as sometimes transient issues can cause failures. 4. If the issue persists, consider using the "Raw data (JSON)" option for normalization instead of "Normalized Tabular Data." This might help you bypass the issue, although it may not be the ideal solution. If you still face issues, I recommend checking the [Airbyte documentation](https://docs.airbyte.com) and [Airbyte forum](https://discuss.airbyte.io) for more information or to ask for help from the community.
j
Ok in case anyone else comes across this annoying error then this might be helpful. The issue in my case was that one of the stream names in the source connector had a space at the end of it (which in my case was in the hands of users creating podio apps), therefore causing some sort of normalization issues when uploading the data to BigQuery. So I simply stripped the stream name in the source connector to ensure no spaces. Problem solved.