Workflow does not display detailed error messages and marks success despite partial failures

lmendoza

Summary:

Workflow does not display detailed error messages and marks success despite partial failures.

Impact:

Developers and workflow users will be receiving false-positives due to the “Completed Message” despite partial failures, that are present when manually triggering processes and through cloudworks.

The expectation is for Workflow to return partial failures, with detailed logs for users to investigate when errors occur.

Partial Failure:

Failure:

Cloudworks Equivalent:

James271Rivera

Summary:
The workflow currently marks jobs as “Completed” even when partial failures occur, and does not surface detailed error messages.
Impact:
This creates false positives for developers and workflow users, who may assume success despite underlying errors. It affects greenskyonline both manual triggers and cloudworks executions, reducing trust in the system’s reporting.
Expectation:
Workflows should return partial failures with clear, detailed logs so users can investigate and resolve issues when errors occur.
Partial Failure Example:
A process may succeed in some steps but fail in others (e.g., data not written to all destinations). Without explicit error reporting, users cannot distinguish between full success and partial failure.