[FAQ Bot] NEW: Why can a Kestra workflow show successful upstream tasks even when downs#133
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
1 participant
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 (The concept explains task success semantics in workflow orchestration and fits under Module 2: Workflow Orchestration.)
Related Issue: #132
Question
Why can a Kestra workflow show successful upstream tasks even when downstream tasks fail?
Decision Rationale
There is no existing FAQ addressing why Kestra marks upstream tasks as successful when downstream tasks fail; the entry provides the exact explanation and belongs in Module 2 (Workflow Orchestration).
Placement Details
module-2kestra-upstream-downstream-success🤖 Generated by FAQ Bot
Closes #132