[FAQ Bot] NEW: Why does Kestra support conditional branching within a single workflow i#145
Merged
alexeygrigorev merged 1 commit intomainfrom Feb 7, 2026
Merged
Conversation
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
✨ FAQ NEW
Course: data-engineering-zoomcamp
Section: module-2 (This question pertains to workflow orchestration design choices and belongs in Module 2.)
Related Issue: #144
Question
Why does Kestra support conditional branching within a single workflow instead of separate flows?
Decision Rationale
The proposal introduces a design topic (conditional branching within a single Kestra workflow) not covered by existing FAQs and fits Module 2 (Workflow Orchestration). A dedicated entry will clarify why this approach is used and how to implement it.
Placement Details
module-2conditional-branching-within-workflow🤖 Generated by FAQ Bot
Closes #144