Affects
Teams that build, operate, or investigate Flowker workflows, especially integrations that consume execution history or rely on telemetry.
What changed
The documentation now describes workflows as graphs of nodes and edges rather than a sequential task model. It clarifies that executed executor, conditional, and action nodes create execution records; trigger nodes start the graph traversal and do not create step records. It also clarifies that OpenTelemetry data is emitted when telemetry is enabled, and that execution investigation uses the API records together with deployment telemetry and logs. The documentation no longer claims a Console execution dashboard. This is a documentation correction; it does not announce a runtime change.
Impact
Classification: Review recommended. Update operational expectations around which nodes appear in execution history and how observability is obtained.
What you need to do
Review workflow runbooks, execution-history consumers, and monitoring guidance. Do not expect trigger nodes to create step records or a Console dashboard to provide the execution view. Enable and connect your telemetry backend if you need OpenTelemetry data.