- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2020 12:52 AM
I created a staging table (u_sales_data_csv_stg) using "Load Data" feature under "System Import Sets". Data got loaded successfully.
When I try to use TABLE API (https://developer.servicenow.com/app.do#!/rest_api_doc?v=jakarta&id=c_TableAPI) to extract data from this staging table, I encounter the following error:
com.glide.sys.TransactionCancelledException: Transaction cancelled: maximum number of SQL queries exceeded
Also, I checked if there is any "Transaction Quota Rule" that is defined in the system to limit this. I did not find any.
Are you aware of any other reason why this is happening?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2020 02:02 AM
I am able to resolve the issue using the following steps:
As part of every "Transaction Quota Rule", there is a "Maximum SQL Queries" attribute. By default, the value for this attribute was 0 for "REST Aggregate API request timeout" transaction quote rule.
Increasing the value of "Maximum SQL Queries" to a higher number resolved the issue.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2020 01:23 AM
while using the table api with steps, which has mentioned on HI article, is it giving you same error ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2020 01:30 AM
Yes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2020 02:02 AM
I am able to resolve the issue using the following steps:
As part of every "Transaction Quota Rule", there is a "Maximum SQL Queries" attribute. By default, the value for this attribute was 0 for "REST Aggregate API request timeout" transaction quote rule.
Increasing the value of "Maximum SQL Queries" to a higher number resolved the issue.