sysparam_limit is not honoured for some objects in my Servicenow instance

[skansal]

Servicenow Object returns less no of records in response than the value specified in sysparam_limit.

I am using the below API call to fetch rows of a table. Ideally it should return 2000 rows but I am getting much less no of rows in response.

https://<instance>.service-now.com/api/now/v1/table/<objectname>?sysparm_offset=0&sysparm_suppress_p...

Could you please suggest is there anything I am missing here?

OR

why sysparam_limit property is not working properly?

[Maik Skoddow]

Hi @skansal 

there are different reasons possible.

One could be that loading 10000 records from a table with much data takes longer that the configured "Transaction Quota Rules". In that case ServiceNow interrupts further loading and you will receive less than 10000 records.

A second reason could be that some data in your table is restricted via ACLs. In that case you will get less records than 10000. See the following article: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0676165 

Another reason could that your table actually has less than 10000 records.

Maik

[skansal]

Hi, I have more than 10000 records in the table and even if I set the sysparam_limit as 100, then also the results are not proper. intermittently I am getting different no of rows for different values of sysparam_limit.

[Maik Skoddow]

Hi @skansal 

without access to your instance and the chance to examine your requests and results and I cannot tell you more than I already have provided.

Maik

[skansal]

Hi, for some objects it is working fine, whereas the issue is observed for some objects like sys_attachment, sys_email, etc. 

any idea what could be reason behind these objects not honouring sysparam_limit