When a rule is triggered without a specific work item context (e.g., using a schedule trigger), and includes a condition that compares two values, the current error messaging can be misleading.

If the condition is not met, the automation logs an error message: "Unable to run this component.",  instead of providing clarity that the condition wasn't met.
The same error will also be shown when there is context, but it will provide the reason why it was not able to run.

Details:

• Current Behavior: When automation rules are triggered without a direct work item context, such as through a schedule trigger, and involve condition comparing values, for instance, from a web request body, if this condition is not met, the error message displayed is "Unable to run this component." and nothing else.
• Proposed Behavior: The error message should explicitly state that the condition was not met. For instance, if the web request body is empty and a condition checks for a non-empty value, the message should indicate, "Condition not met: Expected non-empty value, but received empty." This enhancement would clarify that the rule did not proceed due to the condition evaluating to false, rather than suggesting a misconfiguration.