Instances that upgrade to Fuji and then to Geneva receive REST quota rules intended only for instances created on Fuji or later.

Steps to Reproduce

In order to reproduce this issue you must make a REST call against your instance that will take longer time than the transaction timeout value specified by the quota rule for the specific REST call.

For example, if you call the Table API and retrieve a large data set that takes 2 minutes to download and the quota rule for REST Table API request timeout is 60 seconds, you receive partial data with an error message and status.

Here is an example of the response body:

"name":"Manx Airlines Ltd",
"name":"Rivermain Ltd",
"detail":"Transaction cancelled: maximum execution time exceeded Check logs for error trace or enable glide.rest.debug property to verify REST request processing",
"message":"Transaction cancelled: maximum execution time exceeded"


You must have the admin role to update quota rule records.

  1. Go to the list of the newly created quota rules for REST: /sysrule_quota_list.do?sysparm_query=nameLIKEREST.
  2. Deactivate all rules (change the value of the Active field from true to false).


Related Problem: PRB673025

Seen In

Fuji Patch 10
Geneva Patch 5

Fixed In

Geneva Patch 7
Helsinki Patch 1

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2016-10-24 07:50:52