Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update directed-acyclic-graph.md #191

Merged
merged 1 commit into from
Jun 20, 2024
Merged

Update directed-acyclic-graph.md #191

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/devguide/architecture/directed-acyclic-graph.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down
Loading