Topic
It used to be that if a botflow was scheduled to run unattended frequently, for example, every 2 minutes, if the original botflow was not complete, RPA Central would put the next run into queued status and would run it when the first one was completed.
Instructions
As of version 2.13 of RPA Central, it is expected behavior that if a botflow is running, and it is time for the next instance to run, RPA Central will skip that scheduled run instead of queuing that instance.
This is to avoid the scenario where a customer could end up with multiple instances queued, all just waiting for the current instance to complete.