This is what orchestrator converts the Cron to “Every minute, between 08:00 AM and 06:59 PM”, so there is no way the Trigger Creates any job after 06:59 PM.
That said this is what could have happened, let’s say your process execution time is 5min (From Start to End) one job started running at 06:50 PM, it takes 5 minutes to complete. But, by then 5 new jobs are created on the robot. So, by the execution ends there are 5 jobs in pending state on the robot. I would request you share the details of process execution time (minimum). We can suggest a better schedule based on that.
The idea of queue based trigger is when an Item is added to Queue by a Dispatcher Process the Performer has to be automatically triggered. Hence there is feature as of now to set a time slot for process triggering. For your requirement I would recommend you schedule the Dispatcher Process that adds items to said queue between 18:00 and 08:00 hours, this way the performer is also triggered in that time span itself.