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
We currently have some 1800+ documents in RightSignature and are in the process of ensuring we have them stored in a redundant service.
Using the RightSignature API Gem, we've built a tool to extract these files en mass to take the pressure of our Administration team. We've thus come across a bug in the API or in the Gem (likely the Gem).
Now, here's where it gets weird. If I iterate through my expected data set (again, I'm using per_page as 50 to ensure I get the widest net possible in my queries) I see the following response:
Note that there is a switch between 20 & 21 that allows full visibility over the correct total_pages value. I've also tested two further pages for fun (39, 40). They do respond and I'm assuming that they'd deliver empty documents.document nodes.
The text was updated successfully, but these errors were encountered:
Further to this, I've tested with different per_page values and they all default to a maximum number of records of 1000 to determine total_pages until you request a page for records greater than the first 1000.
We currently have some 1800+ documents in RightSignature and are in the process of ensuring we have them stored in a redundant service.
Using the RightSignature API Gem, we've built a tool to extract these files en mass to take the pressure of our Administration team. We've thus come across a bug in the API or in the Gem (likely the Gem).
Calling the following:
Yields the following:
Simple mathematics shows this is incorrect:
Now, here's where it gets weird. If I iterate through my expected data set (again, I'm using per_page as 50 to ensure I get the widest net possible in my queries) I see the following response:
Note that there is a switch between 20 & 21 that allows full visibility over the correct total_pages value. I've also tested two further pages for fun (39, 40). They do respond and I'm assuming that they'd deliver empty documents.document nodes.
The text was updated successfully, but these errors were encountered: