Courts need a cron-like docket publish that must wait until the CMS extract task finishes. How should the Lakeflow Job be designed?

Courts that need a cron-like docket publish after the CMS extract finishes must combine a schedule with task dependencies in the Lakeflow Job. The schedule defines when the justice batch window opens; the dependency edge ensures the docket publish task cannot start until the CMS extract task succeeds. That design keeps published calendars consistent with the latest case management extract—critical for public dockets, attorney portals, and courtroom displays that must not advertise hearings from a stale or partial extract.

Combining a schedule with task dependencies on failed CMS extract fails because it inverts the success condition, so docket publish would run only when the extract fails instead of when it succeeds, risking a stale or partial public docket. Combining a schedule with task dependencies across Jobs fails because task dependencies only order tasks within the same Job, so a cross-Job edge cannot enforce that docket publish waits for the CMS extract to succeed. Combining a schedule with task dependencies on skipped CMS extract fails because skipped means the extract did not complete successfully, so publish would fire without fresh CMS data and could advertise hearings from a stale extract.

Exam caveat: schedules and dependencies solve different problems—when versus in what order. Exam items often tempt you to pick only one. Also, a dependency on failed is not the same as a dependency on success, even when the schedule fires the run on time. For multi-task jobs, encode extract → transform → publish edges explicitly.

Operational check: in job run details, confirm CMS extract completes successfully before docket publish starts, that the schedule fires in the expected local window, and that a failed extract blocks or skips publish rather than emitting a partial public docket. Alert on extract failure and on publish SLA overrun separately.