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
This is my new connector PR 18893, in which I have used PageIncrement as page strategy and as you can see from the below log in the below outbound API message, the page option is not added in requester
@bala-ceg your logs show that only one page of requests was fetched for each stream slice. Additional pages were not requested because the first page contains fewer records than a page can contain.
I also want to point out that the data seems to be in the "products" field of the response, so you should update the extractor's field_pointer to ["products"]
@girarda, thanks for taking a look at this. I have around 30 records, but I still outwards API request is not sending any page number request. I have the exact config in this airbyte low-code tutorial
@bala-ceg the connector in your PR is interpreting the responses as being only one record because it doesn't know where to find the records in the response.
Current Behavior
This is my new connector PR 18893, in which I have used PageIncrement as page strategy and as you can see from the below log in the below outbound API message, the page option is not added in requester
Logs
The text was updated successfully, but these errors were encountered: