Skip to main content
Question

File not found. exception: repository.exception.directory.notfound in Checkin request

  • July 24, 2023
  • 6 replies
  • 822 views

Forum|alt.badge.img+1

I’m facing this error during the Checkin request, all the bot dependencies are already checked in, and this generic error doesn’t help much, anyone knows a way to see exactly what is the problem with the bot?
This is a bot that have alot dependencies, so I’m not sure what is the problem and what should I do to fix it

Screenshot:
 

 

6 replies

rbkadiyam
Premier Pathfinder | Tier 7
Forum|alt.badge.img+17
  • Premier Pathfinder | Tier 7
  • July 24, 2023

@ezeqpost94  check if you have access for that folder 


Forum|alt.badge.img+1
  • Author
  • Cadet | Tier 2
  • July 24, 2023

Yes, full access.
User role “Creator” assigned:
 


“Creator” Role permissions:

 


Forum|alt.badge.img+1
  • Author
  • Cadet | Tier 2
  • July 24, 2023

I removed all the bot dependencies, and now trying to add one by one, but already in the first dependency I come across this error, how do I know which .png he is referring to? I have no references to .png files in the process, should be from a recorder action.

All the packages are updated to default version

 

 


Forum|alt.badge.img

Facing same issue, How to resolve it?


Forum|alt.badge.img+1
  • Author
  • Cadet | Tier 2
  • July 26, 2023

Hello, I managed to solve this problem with this article below, basically I deleted all the tasks that were cloned in the private repository from users other than mine. It doesn't make any sense to me (what do cloned bots in other users' private repositories have to do with it?), but it worked here...

https://apeople.automationanywhere.com/s/article/After-upgradation-to-V29-the-users-are-not-able-to-check-in-and-check-out-the-bot


Andoni_1
Navigator | Tier 3
Forum|alt.badge.img+10
  • Navigator | Tier 3
  • August 1, 2023

Hello, I managed to solve this problem with this article below, basically I deleted all the tasks that were cloned in the private repository from users other than mine. It doesn't make any sense to me (what do cloned bots in other users' private repositories have to do with it?), but it worked here...

https://apeople.automationanywhere.com/s/article/After-upgradation-to-V29-the-users-are-not-able-to-check-in-and-check-out-the-bot

@ezeqpost94, were you able to delete the cloned bots from other users Private repository without any issue?? Wouldn’t AA throw error if those dependencies are dependencies of those user’s bots? (i.e. any reusable component that is used in several automations)