From 6bbafd8d12a2ed7f1387bd4b28ec5433f1e581e4 Mon Sep 17 00:00:00 2001 From: RizaFarheen Date: Thu, 20 Jun 2024 15:01:38 +0400 Subject: [PATCH] Update directed-acyclic-graph.md --- docs/devguide/architecture/directed-acyclic-graph.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/devguide/architecture/directed-acyclic-graph.md b/docs/devguide/architecture/directed-acyclic-graph.md index f8d08c0b6..c741eca14 100644 --- a/docs/devguide/architecture/directed-acyclic-graph.md +++ b/docs/devguide/architecture/directed-acyclic-graph.md @@ -34,13 +34,13 @@ So a Directed Acyclic Graph is a set of vertices where the connections are direc Since a Conductor workflow is a series of vertices that can connect in only a specific direction and cannot loop, a Conductor workflow is thus a directed acyclic graph: -![Conductor Dag](dag_workflow.png) +![Conductor Dag](dag_workflow2.png) ### Can a workflow have loops and still be a DAG? Yes. For example, Conductor workflows have Do-While loops: -![Conductor Dag](dag_workflow2.png) +![Conductor Dag](dag_workflow.png) This is still a DAG, because the loop is just shorthand for running the tasks inside the loop over and over again. For example, if the 2nd loop in the above image is run 3 times, the workflow path will be: