https://community.blueprism.com/t5/Product-Forum/Timeout-when-start-process-by-CMD/m-p/88223#M38811 Hi, This happens for the resource not logged in or in Idle mode and the version 6.x permit to assign the process before was anyway blocked. could be useful this approach: cmd.exe /c AutomateC.exe /run ..... the return parameter, etc. are returned but is not in wait for the completion  otherwise if you need to wait to start a second process (i.e. after the Login was completed): echo wait 150 seconds timeout /t 150 /NOBREAK > NUL     Fri, 16 Nov 2018 11:59:00 GMT RobertoCarbonet 2018-11-16T11:59:00Z https://community.blueprism.com/t5/Product-Forum/Timeout-when-start-process-by-CMD/m-p/88222#M38810 When I started some process by cmd every time before process start  I must waiting something. Why does timeout occur? For what this timeout needed? Maybe there is a way to get rid of the timeout?  Wed, 14 Nov 2018 12:13:00 GMT https://community.blueprism.com/t5/Product-Forum/Timeout-when-start-process-by-CMD/m-p/88222#M38810 YahorPamazai 2018-11-14T12:13:00Z https://community.blueprism.com/t5/Product-Forum/Timeout-when-start-process-by-CMD/m-p/88223#M38811 Hi, This happens for the resource not logged in or in Idle mode and the version 6.x permit to assign the process before was anyway blocked. could be useful this approach: cmd.exe /c AutomateC.exe /run ..... the return parameter, etc. are returned but is not in wait for the completion  otherwise if you need to wait to start a second process (i.e. after the Login was completed): echo wait 150 seconds timeout /t 150 /NOBREAK > NUL     Fri, 16 Nov 2018 11:59:00 GMT https://community.blueprism.com/t5/Product-Forum/Timeout-when-start-process-by-CMD/m-p/88223#M38811 RobertoCarbonet 2018-11-16T11:59:00Z