#7135 fix: always call writeOutput on connector SUCCEEDED Pull request opened by pvditt Summary • When a connector task succeeds but returns nil outputs (relying on file-based outputs written to remote storage),

writeOutput

was skipped entirely, leaving the

BufferedOutputWriter

without a reader • This caused

ValidateOutput

to fail with "Outputs not generated by task execution" • Always call

writeOutput

on

SUCCEEDED

so the

RemoteFileOutputReader

fallback is used when outputs are nil, matching v1 behavior Test plan • Existing connector plugin tests pass (

go test ./flyteplugins/go/tasks/plugins/webapi/connector/...

) • Run connector tasks (e.g.

examples/basics/connectors.py

) with executor-v2 and verify outputs are resolved correctly 🤖 Generated with Claude Code •

main

• #6583 • fix: always call writeOutput on connector SUCCEEDED 👈 flyteorg/flyte