Schedule recurring ESS job to start immediately after the previous job has completed
SummaryIs it possible to schedule recurring ESS job to start immediately after the previous job has completed?
I am trying to understand what is the best possibly way to schedule a recurring ESS job so that only 1 job is actively running, and the next job starts immediately after the current running job has completed.
The requirement is related to the processing of transactions in an interface to be able close to real-time as possible as the customer has specific cutoff times in their process. There are 2 concerns:
1. If ESS jobs overlap each other when running, it could potentially lead to locking or concurrency issues at a database level.