Just reporting a bug that I discovered because it took me several hours to fix and could be resolved with enhanced error handling.

Essentially, AARI bots will be stuck in queue indefinitely and will never trigger if you delete one of the variables used as input parameter for child task bots within the process. For example in my case, one of my child task bots uses the input variable numCounter which is generated by the main task bot and passed to one if the main bot’s children. In the process of modifying and optimizing my code, I deleted numCounter from the main task bot and removed the the input variable reference from the child bot that uses numCounter. 

Keep in mind I had made several changes, this being one of them. After doing this, any time that I ran this bot from AARI, the bot would be stuck in queue and would never trigger. There would be no error message other than “Bot is in queue and will start shortly”. It was only after hours of troubleshooting that I decided to trigger the main task bot manually instead of from AARI and I was finally given the error message that “The bot won’t start because numCounter, used by one of the child task bots, is missing” (paraphrasing the error message).

Just giving this update because if that error message was given from the AARI interface instead of being stuck in queue indefinitely, this could’ve saved me a lot of time. Hopefully this helps other developers with bots stuck in queue.

Thanks