Skip to content

[FAQ Bot] NEW: Why doesn’t Kestra automatically convert printed task outputs into varia #137

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 2 commits into from
Feb 7, 2026
Merged

[FAQ Bot] NEW: Why doesn’t Kestra automatically convert printed task outputs into varia #137

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f49f399
NEW: Why doesn’t Kestra automatically convert printed task outputs in…
Feb 3, 2026
664b087
Move Kestra stdout variables FAQ from general to module-2 and set sor…
alexeygrigorev Feb 7, 2026
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
7 changes: 7 additions & 0 deletions ...ns/data-engineering-zoomcamp/module-2/021_5a0d2c0e59_kestra-stdout-variables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
id: 5a0d2c0e59
question: Why doesn’t Kestra automatically convert printed task outputs into variables?
sort_order: 5
---

Kestra distinguishes between execution logs and structured outputs. Values printed to stdout are treated as logs for observability, not as structured data. Explicit output definitions are required to persist or reuse values across tasks.