Transaction cancelled: maximum execution time exceeded error getting in sys_user API

[Aakansha2]

Hello,

In service now when I am calling sys_user api with pagination limit 10000 which is default in  in document, getting this below error. I am getting 8461 user account in response and then this error -

{},"error":{"message":"Transaction cancelled: maximum execution time exceeded","detail":"Transaction cancelled: maximum execution time exceeded Check logs for error trace or enable glide.rest.debug property to verify REST request processing"},"status":"failure"}

Please help me how can i solve this error.

[Tony Chatfield1 · Accepted solution]

Hi, I don’t recall a sys_user api so am guessing you mean you are using rest api to connect to sys_user table?

 I think the 10,000 is the max json export row limit? but this does not automatically mean that you will be able to export 10,000 records from every table and the max limit will be impacted by table size\field count record size\content of the fields and the performance of your instance (if this is a PDI? then it has a lot less resource than a prod instance)

 Regardless of the instance type, have you reviewed the system logs to see if they provide any additional details?

Normally I would set a lower export limit (normally 2-3000 records) with sysparam_limit and sysparm_offset to increment/paginate the results, This way I can be sure that my export would
1 run relatively quickly
2 not consume too much system resource at any one time trying to compile a large payload.

Just because you can do something on paper doesn’t mean it will work, or that it is a good idea
and the only way you will know for sure is to debug the issue and identify/understand why the timeout is reached.

[Aakansha2]

Yes I am talking about table api. When i try with pagination limit 5000, it works fine. But is there any other solution with that we can remove this error with 10k itself. as i have 64k user account on portal.

[Tony Chatfield1]

Hi, You can only understand the options you have available to you once you have investigated and understand why the transaction timed out.

Is the data set too large, not record count but payload size?

Are there underpinning scripts, ref qualifiers, ACL's etc that are running slowly and resulting in a timeout?

Some other reason...?

The only way you can find this out is to start by reviewing the system logs, node logs, slow BR logs etc.

[Sraj1]

hello Tony,

where can i find these sysparam_limit and sysparm_offset to make change? i am new to integration