Skip to main content
Ground Control | Tier 1
July 29, 2026
Solved

Unable to Check In Code - AI Automation Engineer Certification

  • July 29, 2026
  • 28 replies
  • 208 views

I am facing an issue while trying to check in code from the Private Repository to the Public Repository in Automation Anywhere Control Room.

I am receiving the following error message:

Insufficient privileges. You do not have the permission "Check In". Please contact the system administrator to get the required permission.

Code: repository.exception.insufficientpermission

Please advise on any steps needed to resolve this issue

Best answer by Aaron.Gleason

@krishnaveni siripuram Ensure your bots are in this folder structure:

/Bots/Users/{your username}

Folders outside that structure cannot be checked in. 

28 replies

Aaron.Gleason
Automation Anywhere Team
Automation Anywhere Team
July 29, 2026

@krishnaveni siripuram Ensure your bots are in this folder structure:

/Bots/Users/{your username}

Folders outside that structure cannot be checked in. 

Cadet | Tier 2
August 11, 2026


 



I am also having issues - what am I getting wrong?

Aaron.Gleason
Automation Anywhere Team
Automation Anywhere Team
August 11, 2026

@JJ07 I just checked your custom role. It has the correct permissions for your custom Public folder…

The custom Public folder exists...

Your account has the correct roles…

Interestingly, each of your failed check in attempts all show “Path” as “Unknown”.  🤨

When I tried to check a file into that same folder, I get this error in the Audit Log:

Unexpected error has occurred during check In exception: org.hibernate.exception.ConstraintViolationException: could not execute statement

I’m going to remove that Public folder and recreate it manually… ah, that worked! 

Go ahead and try checking in your test bot again, or work with the one I checked into your folder.

 

Cadet | Tier 2
August 13, 2026

Hi Aaron,

Thank you for your response.

I am still running into issues unfortunately.


Please let me know if you require me to try anything on my end - or if you would like to setup a quick call?

Kind regards

Aaron.Gleason
Automation Anywhere Team
Automation Anywhere Team
August 13, 2026

@JJ07 Ensure your code is in the /Bots/Users/{your username} folder. You do NOT have permissions to check in files from ANY other folder.

Ground Control | Tier 1
August 15, 2026

Hi ​@Aaron.Gleason 

 

I have the same issue even though I followed the Directory structure you mentioned.

Aaron.Gleason
Automation Anywhere Team
Automation Anywhere Team
August 15, 2026

Hi ​@Aaron.Gleason 

 

I have the same issue even though I followed the Directory structure you mentioned.

I manually deleted and recreated your Users folder in Public. Try checking in again and let me know. By the way, it appears your ID starts with 1Gwf, is that correct?

Ground Control | Tier 1
August 15, 2026

Yes ​@Aaron.Gleason. The id is correct. I have just tried to do check in. It is still the same. 

 

Ground Control | Tier 1
August 15, 2026

Same again ​@Aaron.Gleason !!

Aaron.Gleason
Automation Anywhere Team
Automation Anywhere Team
August 15, 2026

Same again ​@Aaron.Gleason !!

Yeah, I was watching the logs. 😔

I was able to check a file into your folder in Public. Can you see the file? Check it out? Delete it?

Aaron.Gleason
Automation Anywhere Team
Automation Anywhere Team
August 15, 2026

Same again ​@Aaron.Gleason !!

Yeah, I was watching the logs. 😔

I was able to check a file into your folder in Public. Can you see the file? Check it out? Delete it?

Something is broken in the CR specific to your account. Not your fault or anything you did. I need to engage our engineering team to figure this out. 

Ground Control | Tier 1
August 15, 2026

The issue was with Folder name being Case mismatched. I created Folder name all lower case in Private repository and now I matched the case with Public repository’s folder name. It is working perfectly fine. Thank you  ​@Aaron.Gleason 

Aaron.Gleason
Automation Anywhere Team
Automation Anywhere Team
August 15, 2026

The issue was with Folder name being Case mismatched. I created Folder name all lower case in Private repository and now I matched the case with Public repository’s folder name. It is working perfectly fine. Thank you  ​@Aaron.Gleason 

Oh, wow. 😯 Good troubleshooting!

Ground Control | Tier 1
August 15, 2026

Thanks 😊