@SankeerthanaB1595

The only configuration where you can define start time is daily/weekly configuration but that will not give you the option to configure for iteration because that is for multiples times a day. This combination of configuration cannot be achieved with single Job Scheduler.

You can use multiple times a day configuration to run it after every hour but you cannot make sure that it will start at 12:00 AM only post deployment. It will depend on deployment time and the scheduler configuration

@SankeerthanaB1595

We don't have direct configuration to do so, but we can achieve it by following option

1. we can config same Job Schedulers on Multiple times like, JS1 -- 12 AM, JS2 --1AM, JS3 --2AM and JS4 -3AM

2. Config Job Scheduler runs Multiple times a day every 10mins, check in the JS activity whether the time is equals to your required time (current Time = 12AM/1AM/2AM/3AM) and execute the rest of the steps else Exit Activity.

@SankeerthanaB1595 

To run a job scheduler at 12AM, 1AM, 2AM, and 3AM every day, you can create a job scheduler with a custom schedule using the cron expression 0 0 0-3 * * ?. This will make the job run once every hour from midnight to 3AM. After deployment to production, make sure the job is not active immediately. You can disable it before deployment and enable it just before 12AM so that the first run happens at midnight. Also, check in Admin Studio that the job is assigned to the right nodes and confirm the “Next Run Time” is set to 12AM. This setup helps ensure the job runs only at the specific times and not immediately after deployment