SugarClub will be undergoing scheduled maintenance and will be inaccessible beginning on Friday, 10 April 2026 (15:00 UTC | 11am EDT | 1am AEST on 11 April).
This maintenance period will end on 
Monday, 13 April 2026 (12:00 UTC | 8am EDT | 10pm AEST). 

PLEASE NOTE: THIS MAINTENANCE PERIOD WILL START SHORTLY

GET /Reports/:record/records is not paging and results in 500 Internal Server Error.

Hi everyone!

I’m working with the SugarCRM API (v11_25) and running into an issue when retrieving report data using the `/Reports/:record/records` endpoint.

According to the documentation (doc reference: /Reports/:record/records GET - Sugar Support) , this endpoint supports the `max_num` and `offset` parameters for pagination. However, these parameters appear to be ignored. Regardless of the values I pass.

For example:

REQUEST
>GET https://{instanceurl}/rest/v11_25/Reports/{recordId}/records?max_num=20

RESPONSE

Contains all report records, with next_offset = -1.


In this case the report I am requesting has only 161 records and they are all returned despite max_num being set to 20.

While small reports are successfully returned, once a report contains a very large number of records, the API still attempts to return the entire dataset in a single response. This results in a very large payload, which I believe is causing the 500 Internal Server Error.

At the moment, this prevents us from loading large reports through the API. 

Is this a known issue? Is there any workaround or configuration change that allows paging results to avoid the large payload and the `500 Internal Server Error`? 

Please let me know if there is a known fix to this or if you have any questions!

Thank you in Advance!