I am just wondering if this is an issue for me or the following is normal. In the event that a published Botflow stops/fails, we normally would go into the Bot to see what the issue was. It could be as simple as the date that was being entered in a date field was missing a digit. In that case, the date would be adjusted and the Botflow would be kicked off again from the Bot. We recently upgraded to version Bot 17.0.6/RPA Central 2.0.5. Now when the failure occurs, I am unable to kick the script off after a failure. I am however able to use the down arrow to step through the process. I end up having to close everything and then restart it from RPA Central. Thanks in advance!