You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been told by the Stitch Support team to write in here, since the Stitch Open Source Engineer regularly reviews issues submitted to GitHub issues on Singer repos.
I have exactly the same issue as #6 . The developers provided a fix by chunking into more searches with a search interval set in the configuration (default=14 days), but I'm hitting the 10k row limit when calling the search endpoint from the Zendesk chat API via the Stitch interface. What I'm missing here is to be able to fully configure this tap in Stitch. The Stitch interface only lets the user to configure the start date (and the access token, of course) from this tap.
Instead of asking for reducing the default interval to 7 days, I wonder if it would be possible to have the search interval available in the Stitch interface.
Thanks in advance for your help.
Cheers,
Jose
The text was updated successfully, but these errors were encountered:
Hello there,
I've been told by the Stitch Support team to write in here, since the Stitch Open Source Engineer regularly reviews issues submitted to GitHub issues on Singer repos.
I have exactly the same issue as #6 . The developers provided a fix by chunking into more searches with a search interval set in the configuration (default=14 days), but I'm hitting the 10k row limit when calling the search endpoint from the Zendesk chat API via the Stitch interface. What I'm missing here is to be able to fully configure this tap in Stitch. The Stitch interface only lets the user to configure the start date (and the access token, of course) from this tap.
Instead of asking for reducing the default interval to 7 days, I wonder if it would be possible to have the search interval available in the Stitch interface.
Thanks in advance for your help.
Cheers,
Jose
The text was updated successfully, but these errors were encountered: