Orchestrator shedule doesn't work as it supposed - CRON expression

Hi everyone,

I’m facing an issue with orchestrator shedule using CRON expression.
CRON expression triggers job from 8am-4pm on every 20 minutes.

The problem is that jobs get triggered after 4pm.

What could be a possible fix for that problem?

Thanks in advance.


Can you please show us CRON expression you are using here. So that we can check and help you.

Of course.
0 0/20 8-16 ? * MON,TUE,WED,THU,FRI *


CRON expression looks fine. I guess one job is pending state which is triggered earlier because of that it is running after 4 PM.

Is Single or multiple jobs running after 4 PM ?

It’s a single job running every 20 minutes.


That I understood.

How many jobs getting triggered after 4 PM ?

Last time it was 2 jobs that was running after 4pm.


If any early triggered jobs are in Pending state then those jobs may be executed after 4 PM but no new job will triggered after 4 PM as per your CRON expression. It looks perfect.


Your expression looks fine

But let me tell you what are the possibilities of getting into pending state

  1. One as you said your process is run for every 20 mins
    If that’s the case let’s take like bot is about to run by 3:45 PM
    But early run to that took more time to execute and because of which the run at 3;45 would have got into pending state
    This could be one scenario

  2. Another scenario is there could another bot running in same machine sharing the license runtime
    And if that bot got triggered by the same time when a schedule of your bot is set then it will obviously in pending state until license is available for this bot to execute

Hope this would help you

Cheers @bp777

@bp777 - I would agree this is most likely the case. If you do not want the jobs to continue after a set time. You can configure the Triggers to Stop Job after 20 minutes, this may not be appropriate for your specific scenario depending on how critical it is for it’s job to compete an entire run to completion.