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
{{ message }}
Repository navigation
ListLogsRequestParameters is missing "from" and "take" for log checkpoint search #990
In the docs for the log search endpoint (as well as the as a previous version of the management SDK) it was possible to do a search from a log checkpoint.
To search from a checkpoint log ID, use the following parameters:
from: Log Event ID from which to start retrieving logs. You can limit the number of logs returned using the take parameter. If you use from at the same time as q, from takes precedence and q is ignored.
take: Number of entries to retrieve when using the from parameter.
I can't find these parameters any more. Using the previous version my code looked like this:
Checkpoint pagination support is currently missing from the ListLogsRequestParameters in the SDK. In the meantime, you can use offset pagination as a workaround.
The underlying issue stems from the Logs endpoint API not handling pagination metadata as expected. We are actively working on a fix for the API specification, and once that is complete, we will update the SDK to include full support for checkpoint pagination.
We apologise for any inconvenience this has caused. While we don't have a firm timeline for the fix, we will update this issue as soon as we have more information.
Hope this helps! Let us know if you need anything else.
Hi! I'm not sure what you are referring to when you say "offset". I guess you mean the page / per_page flags?
In that case I'm a bit worried about the part:
Auth0 limits the number of logs you can return by search criteria to 100 logs per request. Furthermore, you may paginate only through 1,000 search results. If you exceed this threshold, please redefine your search or use the get logs by checkpoint method.
That is a no go for us since we are going through a lot more then 1000 entries and is also the reason why we went with the checkpoint method in the first place.
Activity
kailash-b commentedon Apr 30, 2026
Hi @niklashedlund1337 👋
Thanks for reaching out.
Checkpoint pagination support is currently missing from the
ListLogsRequestParametersin the SDK. In the meantime, you can useoffsetpagination as a workaround.The underlying issue stems from the Logs endpoint API not handling pagination metadata as expected. We are actively working on a fix for the API specification, and once that is complete, we will update the SDK to include full support for checkpoint pagination.
We apologise for any inconvenience this has caused. While we don't have a firm timeline for the fix, we will update this issue as soon as we have more information.
Hope this helps! Let us know if you need anything else.
niklashedlund1337 commentedon May 4, 2026
Hi! I'm not sure what you are referring to when you say "offset". I guess you mean the
page/per_pageflags?In that case I'm a bit worried about the part:
That is a no go for us since we are going through a lot more then 1000 entries and is also the reason why we went with the checkpoint method in the first place.
Am I correct in my assumption?
crapitan commentedon Aug 19, 2026
Any news on this?