A few ideas off the top of my head:
The process script inside of the object could detect at what time it was launched and react accordingly. (This would make it hard to test it at different times of day though.)
Another idea is to put the job inside of a workflow, and have a workflow task precondition rule check the time it executes and react accordingly. (This would interfere with testing the workflow at different times of day)
Another idea is to schedule a separate workflow to run right at 13:00 every day, and if it detects that your job hasn't started yet, it would react accordingly. I usually try to do this sort of trickery with precondition rules on top of an alert task to either Run or Skip the task.
There is also a new "Fulfillments" feature in the product which can be accessed via the "Process Monitoring" perspective. I haven't played with it yet, but I wonder if it might be able to satisfy your requirement?
------------------------------
Pete
------------------------------
Original Message:
Sent: 01-17-2020 02:51 PM
From: Lennie Currington
Subject: Run Times
I know that you can give a job the maximum run time and then alert based off of that. My question is can I give a job a time that it should start by and then alert off of that. As an example if I want job A to start by 13:00, can I get an alert if it starts at 13:01 instead?