Skip to content

[FAQ Bot] NEW: Why can a Kestra workflow show successful upstream tasks even when downs #133

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

Merged
alexeygrigorev merged 1 commit into from
Feb 7, 2026
Merged

[FAQ Bot] NEW: Why can a Kestra workflow show successful upstream tasks even when downs #133

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
8 changes: 8 additions & 0 deletions ...ineering-zoomcamp/module-2/009_70722b98b6_kestra-upstream-downstream-success.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
id: 70722b98b6
question: Why can a Kestra workflow show successful upstream tasks even when downstream
tasks fail?
sort_order: 9
---

Kestra executes tasks independently according to defined dependencies. A task is marked successful if its own execution completes without error, regardless of downstream failures. This makes it possible to inspect intermediate outputs and logs (such as file size computation) even if later database or merge steps fail.