Incorrect second showing in Next Run Time if time based Trigger is set with a zero second.
Issue / Error:
Incorrect value is showing in Next Run Time of defined Time-based Trigger in Cloud Orchestrator. If the second was set as 0 in the trigger, then the second in hover text will always have some delay.
It can be only reproduced on Cloud environment, on-premise is normal.
For example, if cron is set as 0 10 12 * * ?, but the Next Run Time shows 12:10:23 which is expected to be 12:10:00. The API shows the same incorrect value in StartProcessNextOccurrence field (in UTC).
However, when cron is set as 1 10 12 * * ?, the Next Run Time shows 12:10:1 which is correct.
Resolution: This is a new feature since 2023-07, details can be refer to the Cloud Release Note (https://docs.uipath.com/orchestrator/automation-cloud/latest/release-notes/release-notes-july-2023#trigger-execution-changes).
The vast majority of process schedules start at second 0 which creates a sort of contention at that time, so now Orchestrator tries to spread schedules at different seconds.
This is something that benefits the users and helps UiPath systems to handle the load. Having less contention decreases the chances of triggers failing to create jobs.
As an alternative, update the second part of the cron expression to 1.