We have moved to a new documentation platform. This section is no longer supported. For the up-to-date information, see How to troubleshoot business process in Control Tower.
Sometimes a business process that was successfully tested locally stops working after publishing to Control Tower. There can be different reasons that require in-depth investigation and troubleshooting.
Usually, you can see that a process has failed in Control Tower. In most cases, it will look similar to the screenshots below:
Follow these basic steps to troubleshoot the business process.
Make sure you have enough free memory and free drive space on the machine where your business process is running. If you see a lack of drive space, for example, free space is 5% from the whole drive size, remove unnecessary files. Before removing, investigate which files you can remove and which ones you cannot.
If you have a Windows Server machine and several additional bots, make sure that all Remote Desktop Connection windows are started. The number of RDC sessions should be equal to the number of additional bots selected during the product installation. For example, if you selected five bots while installing, five RDC session windows should be opened.
Since version 2.3.0, you can see the number of additional active bots on the Components tab.
If you use OCR actions in your business process, make sure that OCR is running and you have the required number of available OCR pages. You can check the OCR status and the number of the pages left on the Components tab as well.
The OCR status, according to the indicator color, can be:
If you found something that can be fixed while performing these steps, try to fix it yourself, and then restart the business process. In some cases (for example, if you have renewed the OCR license), you may require to restart the whole application and/or the machine. Run your business process after reboot and check how it works.
When you have followed all basic steps and still haven't found any issues with them, you need to investigate specific business process errors.