On premise! Update set export fails due to 300 second timeout

[oliolio]

Hi,

We're running Servicenow on Premise and where we have 4 different environment. Development, acceptance, production and test.

We've recently completed a large project where we have developed a new service portal. In the development environment the changes are spread out over a number (26) different update sets with around 20 000 updates in total. They also belong to different application scopes. All of them have dependencies amongst eachother and need to be moved as a batch to the acceptance environment to ensure that we do not encounter errors along the way.
However, when trying to export the update set batch the system hits the 300 second timeout and we are unable to export the updates.

Does anyone have any suggestions? 

We've tried running the below script but no luck there.

"var updateSetExport = new UpdateSetExport();
var updateGR = new GlideRecord('sys_update_set');
updateGR.get('sys_id', 'SYS_ID');
updateSetExport.exportUpdateSet(updateGR);"

BR 
Ola Thews

[oliolio]

Ah, i see. That is not what we're looking for as it's not the user session we have an issue with, rather it is the transaction quota itself. 

[oliolio · Accepted solution]

Found it! Transaction quota rules governs this and we are able to change the quota from there. We'll see if it helps.