Skip to main content

Job Dependency and Auto Restart (Preview)

  • Nov 17, 2026 6:54 PM UTC
  • 0 replies
  • 0 views

This is a short preview of a Knowledge Base article. The full article is available to logged-in Continuous Community members.

Summary

Explains why a job dependency may never be resolved even though the job it depends on shows Finished OK in the job history. When the dependent-on job is set to restart automatically when it finishes OK, it returns to a waiting state so quickly that the dependency never sees the Finished OK status. The article shows a workaround that moves the restart to a container job around a sub schedule.

Applies to

OpCon job dependencies · automatic restart · container jobs · sub schedules

Topics covered

  • The symptom: Finished OK in history but the dependency stays unresolved
  • Why the automatic restart causes it
  • Using a sub schedule and container job to restart the whole group

Keywords

job dependency not resolved, auto restart, restart when job finishes OK, Requires Finished Ok, Wait Start Time, container job, sub schedule, job history, dependency issue

Read the full article (Continuous Community login required)