RPA Control Tower fails on


#1

After resolving the issue here, Create Process / Schedule - Same Bot Task, Different data sets … by leveraging 2 records to process 2 different sets of customer data, it runs great when only processing a short time for the first customer.

However, when the bot begins processing the first row of the input data which can take up to 2 hours to complete. While in the middle of this, it appears the second row of the input data is getting the following error as it waits for the bot to finish. " Error forwarding the new session Request timed out waiting for a node to become available.
Command duration or timeout: 300.01 seconds".

  1. Can the node timeout be extended?
  2. Does control tower do the same if 2 scheduled jobs try to execute concurrently?
  3. Is there an alternate method to handle this?

Here is the error file from Control Tower.
Copy of events_root_6305959f-61d3-4b10-bee0-69113a008a03_2017-10-31 04-39-00.xlsx (10.0 KB)


#2

hi @jdoering,

However, when the bot begins processing the first row of the input data which can take up to 2 hours to complete.

Is this an expected behavior? One record execution takes 2 hours?


#3

Yes - The first record points to a check that must be processed against 2-300 line items. Cant do as single line items in the system, all have to be part of the cash application for a single check.


#4

@jdoering, thanks for reporting this issue.

Currently, RPA Express license of Control Tower does not allow multiple bot executions more that 300 seconds.

We will try to fix this in 1.1.8


#5

Thanks. As a workaround, if a schedule is set up to run hourly and the bot is still executing, I assume the schedule will not execute concurrently but will it queue up, fail, or just not run if the bot is unavailable?


#6

But now you can do a workaround:

  1. go to C:\RPAExpress\Workfusion\tomcat\conf
  2. open the workfusion.properties file
  3. append the following line: bot.source.thread.pool.size.default=1
  4. restart the Control Tower

#7

Thanks for that. However, when I ran that, the jobs were running concurrently and were overwriting each other instead of waiting on the other to finish.


#8

make sure that all previous process instances are stopped

and restart the Bot manager as well. Better to click the Restart all)