Delay Start Job Execution

Feedback Orchestrator
1

Hello,

It would be great to add a “Delay” feature on the “Start Job” page.

Use case: For example, I need to execute a trigger in 4 hours for business reasons, and I only need to do it once.
However, when I use “Run job,” I can only execute it immediately. Adding a “Delay job” option would therefore be very useful in certain scenarios.

Thank you

3

You can create one-off time trigger for this purpose.

The truth is that it requires creating a cron expression, which is not convenient at all :frowning:

Cheers

4

@simon.l

Ideally what @J0ska said is what you need to do…creating a one-time trigger is what delay run is

@J0ska - there was one cron expresso library.we can use it to generate the crons.

cheers

5

There are indeed many tools that can be used to create cron expression.

The question is why this is not integral part of Orchestrator as another option like “Frequency: one-time” followed by selection of specific date/time…

Cheers

6

@J0ska

Valid ask. May be a right request or usage need was not given :stuck_out_tongue:

Lets ensure this thread goes up

cheers

7

Clearly the solution here is to update your process, add a 4hour delay at the start, run it and then revert the process tomorrow.

8

It could be a nice feature, but I hate all the suggested workarounds here.

If I had to do this, I would use the ‘New Item Added To Queue’ trigger

Then instead of trying to run a job with a delay I make a queue item with a postpone time set. The queue trigger will start a new job as soon as the queue item reaches its postpone date. Far more elegant than needing to mess with the API to make one of time triggers with Cron expressions that need to then be removed later, especially in terms of passing job arguments etc, can just be passed in the queue item.