If the trigger was running twice then it would appear in Octopus as two separate runs. Are you sure that the service is actually being restarted at 4am? When configuring the trigger you can set the timezone and I’m wondering if perhaps the wrong one has been selected causing it to run at 3am rather than 4am?
That is unusual indeed, I don’t see how Octopus could be running this without anything being logged. Is the runbook a simple script to restart a service? It doesn’t create a scheduled task within Windows Task Scheduler or anything similar?
I can see there are 5 triggers for that runbook, would you be able to send a quick screenshot of them?
Also, would it be possible to disable this trigger for a day as a test to see if the service still gets restarted at 3:30?
These are the 5 triggers which you’ve seen in the previous screenshot. These 5 triggers is for separate set of environments. Please have a look on screenshot below.
The other option would be to amend the runbook script so that it writes a timestamp to a logfile somewhere on the machine when it runs. This would require a bit more work though.
It’s mainly just a test to confirm that it is definitely this runbook and trigger that is causing the restart of the service at the wrong time.
The only other thing I can think to check is the Tasks section in Octopus and filtering on Task Type: Runbook run to see if there are any around 3.30. This is on the off chance that the task isn’t appearing in the runbook section.
