Job Recurring Trigger end date not working as expected
Trailblazer Community

Job Recurring Trigger end date not working as expected

Commerce Cloud Admin

Last updated 2020-04-18 ·Reference W-5611724 ·Reported By 2 users

In Review

Summary
The end date is currently interpreted with a granularity of days. So if you define an end date of 11/12/2018 01:00pm; the job will be executed until the end of the days, means 11/12/2018 11:59pm. A new bug is open for this issue since the hours and minutes are ignored and job will be executed until the end of the day.

Repro
Create a job (new job framework) with an enabled recurring trigger that runs every 3 minutes, from a start date of now until an end date of now+10 minutes.
There are job history entries after the trigger's end date.
Root cause:
The end date is currently stripped by the framework down to a granularity of days. This means the job will continued to be executed until the end of the day of the defined end date has been reached. This is how the old job framework works.
The new job framework allows to define end dates with day, hours and minutes but the hours and minutes are ignored.

Workaround
There is no work around as the job will be executed until the end of the day as the hours and minutes are ignored.

Reported By (2)

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.