Have a very similar use-case years ago..

The simplest way of thinking here is a “system throughput”. Eventually you want both tasks running daily, and technically you have to keep them happening one by one. Let’s ask a few questions that should help here:

1. Can we skip the day?
2. Can we run a job on next day?
3. Running job during next business day would be as simple as running it today, or require dirty hacks?

This is not only about keeping cycle, this is also about your ability to execute job with correct inputs and complexity of execution process.

I end up with understanding that no matter what  ,job need to be done within a same day, i.e running tomorrow today’s job is a big issue.

As a consequence, the monitored sequence is on day level. If job fails I have to stop batch process and wait for fix. Run on a next day (historically) is a totally different process that must acknowledge datetime change in my use case.

I had a very similar use-case years ago.

The simplest way of thinking here is a “system throughput”. Eventually you want both tasks running daily, and technically you have to keep them happening one by one. Let’s ask a few questions that should help here:

1. Can we skip the day?
2. Can we run a job on next day?
3. Running job during next business day would be as simple as running it today, or require dirty hacks?

This is not only about keeping cycle, this is also about your ability to execute job with correct inputs and complexity of execution process.

I end up with understanding that no matter what, the job need to be done within the same day, i.e, running today’s job tomorrow is a big problem.

As a consequence, the monitored sequence is on day level. If the job fails I have to stop batch process and wait for a fix. If I run the current day's work on a future day (historically), that's a totally different process that must acknowledge datetime change in my use case.