Hello ​@Melqui 4737. Having an on-premises control room means you (or an administrator) have access to all the logs on the server side of the house.

Personally, I would start by checking SQL Server for any database errors that occur during this check-out process. To do this, go to SQL Server Management Studio (SSMS) and check out Management > SQL Server Logs. You may be able to keep that open while trying to check in a file, preventing you from having to look through too many logs.

Also check your servers’ free RAM and storage space available.

What build number is your control room? 

Hi, Aaron. Thanks for your answer. The build number of my control room is Automation 360 build 22278

Thanks, ​@Melqui 4737. That means you’re running version .32 of our software. The current version is .38, which may have some fixes for the control room. 

I would recommend taking a look through the release notes here for .33 and later to see if there is something that seems to match up with what you’re seeing.

https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/release-notes/cloud-release-notes.html

If you do see something odd, feel free to post it here, or if there is sensitive data, send it to my email at aaron.gleason@automationanywhere.com and I’ll see if I can give you other things to look for.