About run dates

Updated: September 22, 2025

All Data Quality Jobs that run in Data Quality & Observability have a run date, represented as rd in the code, which marks the start of each run or time slice interval. By default, a run date is the date when a job is created. However, you can set a past date as the run date. When you include a time slice, the job must have a run date end, represented as rdEnd, to indicate the end of the time slice interval. The run date end value must always be later than the run date.

You can find the run date in the following locations in the Data Quality & Observability UI:

• In the JSON tab of the Review step when you create or edit a job.
  • The startTime parameter represents the run date.
  • The endTime parameter represents the run date end.
• Along the x axis of the run history chart in the Profile tab of the Job Details page.

The following scenarios detail how run date and run date end work in Data Quality & Observability.

Scenario 1

Repeat setting	Time slice enabled?	Back runs enabled?
Never	No	No

When you create a job without a run schedule, time slice, or back runs, the run date is the date the job is created.

For example, if you create a job on November 20, 2025, the run date is 2025-11-20. Since a time slice is not enabled, there is no run date end value.

Scenario 2

Repeat setting	Time slice enabled?	Back runs enabled?
Weekdays	No	No

Similar to the first scenario, this job does not have a run date end. However, because it is configured to run automatically on weekdays, the run date is the run start time on the scheduled day.

For example, if November 20, 2025 falls on a weekday and a job is configured to run on weekdays, the job that runs on November 20 will have a run date of 2025-11-20.

Scenario 3

Repeat setting	Time slice enabled?	Back runs enabled?
Never	Yes	No

This job has a run date end because a time slice is enabled. When a time slice is enabled but the job is not configured to run on an automated schedule, the current date becomes the run date end, and the run date represents the start of the time slice interval.

For example, if a job runs on November 20, 2025, with a time slice of 2 days, the run date will be 2025-11-18, and the run date end will be 2025-11-20.

Scenario 4

Repeat setting	Time slice enabled?	Back runs enabled?
Never	Yes	Yes

The basis of this scenario is similar to the third scenario: the current date becomes the run date end, and the run date represents the start of the time slice interval. However, there is a key difference. Because both back runs and time slice are enabled, the job initially runs based on the specified time slice interval, starting on the date you initiate the run. Then, it processes the back runs while factoring in the specified time slice for each back run.

For example, if you run a job on November 9, 2025, with a time slice of 2 days and a back run of 10 days, the first run will have a run date of 2025-10-28 and a run date end of 2025-10-30. The second run will have a run date of 2025-10-29 and a run date end of 2025-10-31, the next will have a run date of 2025-10-30 and a run date end of 2025-11-01, and so on until the final run, which will have a run date of 2025-11-07 and a run date end of 2025-11-09.

For a complete breakdown of this scenario, refer to the following table.

Scenario 5

Repeat setting	Time slice enabled?	Back runs enabled?
Weekdays	Yes	No

When a time slice is enabled and the schedule repeat is set to weekdays, jobs run every weekday with a run date and run date end that reflect your time slice setting. Even though the scheduling repeat is set to weekdays, if you set a time slice of one or more days, at least one weekend day included in the run.

For example, a job that initially runs on Thursday, November 20, 2025, with a time slice of 2 days and a repeat setting of weekdays will begin with a run date of 2025-11-18 and a run date end of 2025-11-20. The next job will run on Friday, November 21, 2025 with a run date of 2025-11-19 and a run date end of 2025-11-21. Because November 22 and 23 are not weekdays, the next job will run on Monday, November 24, 2025 with a run date of 2025-11-22 (a Saturday) and a run date end of 2025-11-24. This pattern continues until the automated run schedule either changes or is disabled.

For a 2-week breakdown of this scenario, refer to the following table.

Scenario 6

Repeat setting	Time slice enabled?	Back runs enabled?
Weekdays	Yes	Yes

When both time slice and back runs are enabled, and the schedule repeat setting is set to weekdays, the back runs behave like scheduled jobs in the past that are created immediately. The weekday schedule also continues to repeat on future weekdays.

For example, a job that initially runs on Thursday, November 20, 2025, with a time slice of 2 days, a repeat setting of weekdays, and back runs set to 14 days, will begin with a run date of 2025-10-29 and a run date end of 2025-10-31. Because the weekend separates the first back run from the second, the next back run will occur on the following Monday with a run date of 2025-11-01 and a run date end of 2025-11-03. The back runs will continue in chronological order, from oldest to most recent, until the final run, which is the date the job is executed. In this case, the initial job execution is on November 20, 2025, and has a run date of 2025-11-18 and a run date end of 2025-11-20.

The next scheduled job run will be on Friday, November 21, 2025 and will have a run date of 2025-11-19 and a run date end of 2025-11-21. Because November 22 and 23 are not weekdays, the next run will be on Monday, November 24, 2025, with a run date of 2025-11-22 (a Saturday) and a run date end of 2025-11-24. This pattern continues until the automated run schedule either changes or is disabled.

For a 30-day breakdown of this scenario, refer to the following table.