Currently, explicit pagination on the filter() and all() endpoints is explicitly forbidden (ref). This can lead to problems where the default timing plus page size (50 when I tried it against demo.nautobot.com) is too much load for the system, causing timeouts or similar errors to happen. This paging behavior happens here.
My suggestion would be to keep this default behavior, but allow the user to optionally control paging (i.e. pass limit + offset) themselves so they can control their request size + timing with values that work on their system.
Currently, explicit pagination on the
filter()andall()endpoints is explicitly forbidden (ref). This can lead to problems where the default timing plus page size (50 when I tried it against demo.nautobot.com) is too much load for the system, causing timeouts or similar errors to happen. This paging behavior happens here.My suggestion would be to keep this default behavior, but allow the user to optionally control paging (i.e. pass limit + offset) themselves so they can control their request size + timing with values that work on their system.