Image Recognition creating BMP Files? -- a360 If > Image Recognition

  • 14 December 2022
  • 3 replies

Badge +3

We just realized that the image recognition in the IF Image Exists command is creating bmp files in the 

botrunner’s C:\ProgramData\AutomationAnywhere\BotRunner\Logs\IR folder.


The command is creating a source bmp file for what is currently on screen and also a copy of the image it’s searching for.  As you can imagine, the folders noted above have ballooned in size. 



Does anyone know why this is happening and how to prevent these files from being created?  We can create a task to clear out these folders, but that’s not really the most efficient solution…



We are using Automation 360 control room build 11499.


The clients are using Bot agent version21.120.




3 replies

Userlevel 3
Badge +6

Dear @Justin107544,


It is likely that the IF Image Exists command is creating these BMP files for logging purposes, so that you can review them later to see what images the bot was looking for and whether it was able to find them. If you don't need these logs and want to prevent the BMP files from being created, you can disable logging for the IF Image Exists command by following these steps:

  1. Open the Automation Anywhere Control Room and go to the "Settings" tab.

  2. Select the "Logging" option from the left menu.

  3. Scroll down to the "IF Image Exists" command and uncheck the box next to it.

  4. Click "Save" to apply the changes.

After you have disabled logging for the IF Image Exists command, the BMP files should no longer be created in the IR folder. Keep in mind that this will also prevent any other logging information from being recorded for this command, so you won't be able to review it later.



Badge +3

Thanks Zaibi but we do not see those options in the control room.  We might be on different versions.

Userlevel 5
Badge +9



I’ve found a twice of references:

The KB above mentions we can modify logging setting in config files, but i didn't find explicitly any related with  folder IR in these files 

The following KB mentions a issue related with that folder, so it seems can be deleted.