Hitting 10m row limit on Zuora and having OAuth issues in forked connector

  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: Debian
  • Memory / Disk: 16GB/200GB
  • Deployment: Docker on GCP VM
  • Airbyte Version: 0.42.0
  • Source name/version: airbyte/source-zuora 0.1.3
  • Destination name/version: airbyte/destination-bigquery 1.2.18
  • Step: During sync


  • Airbyte uses the Zuora Data Query API.
  • The Data Query API has a 10 million row limit for input.
  • Input rows are filtered by WHERE in SQL.
  • If filtering on UpdatedDate using a string cast with TIMESTAMP and the string has 6 decimals for fractions of a second, that filter is seemingly ignored, making you hit that 10m row limit in a big table.
  • Version 0.1.3 of source-zuora outputs a string with 6 decimals.


-- Working query:
select count(*)
from payment where
updateddate >= TIMESTAMP '2023-01-02 00:00:00.000 +00:00' and
updateddate <= TIMESTAMP '2023-01-07 00:00:00.000 +00:00'

-- Failing query:
select count(*)
from payment where
updateddate >= TIMESTAMP '2023-01-02 00:00:00.000000 +00:00' and
updateddate <= TIMESTAMP '2023-01-07 00:00:00.000000 +00:00'

The last query hits the 10 million row limit: Query failed (#): Input Rows for payment exceeded limit (10000000)

I have fixed this issue in this PR.

If I publish that connector and use it as a custom connector in Airbyte I get several other issues though, like:

  • oauth not working anymore (workaround here),
  • Airbyte running duplicate queries (two identical queries, using the same UpdatedDate window) and then spamming at least a few hundred DESCRIBE <table> queries. I haven’t let it run to see if it finishes.

I only run one table at a time, so first it queries the table twice, and then it spams for description of the same table.

Does this sound familiar to anyone? Have I missed something obvious when deploying the forked custom connector?

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team