Checklist
Describe the bug
Automation steps that require a resource to be selected can report unclear configuration errors when that selection is missing. Users cannot easily tell which field needs to be configured or how to fix the problem.
In the reported example, running an automation with a Run Function step without selecting a function produced:
The Function automation step is missing required configuration
The reviewer identified the missing function selection by inspecting the code, but a customer should be able to identify and resolve the problem from the error message.
This should be addressed across all automation steps that require a selection, including Query rows, rather than only Run Function.
To Reproduce
- Create an automation and add a Run Function step.
- Leave the function selection empty.
- Run the automation.
- Observe the generic missing-configuration error, which does not identify the missing function selection.
Review equivalent missing-selection cases in other automation steps, including Query rows.
Expected behavior
Validation errors identify the automation step and the required selection that is missing, with a clear instruction for resolving it. For example, Run Function could report: "Select a function in the Run Function step before running this automation."
Apply equivalent messages across automation steps that require a selection so users can fix their configuration without inspecting code or contacting support.
Additional context
Reported in this review comment: #19737 (comment)
This is out of scope for PR #19737, which moves Functions into workspace resources. The underlying usability problem affects automation steps generally and should be handled separately.
Checklist
Describe the bug
Automation steps that require a resource to be selected can report unclear configuration errors when that selection is missing. Users cannot easily tell which field needs to be configured or how to fix the problem.
In the reported example, running an automation with a Run Function step without selecting a function produced:
The reviewer identified the missing function selection by inspecting the code, but a customer should be able to identify and resolve the problem from the error message.
This should be addressed across all automation steps that require a selection, including Query rows, rather than only Run Function.
To Reproduce
Review equivalent missing-selection cases in other automation steps, including Query rows.
Expected behavior
Validation errors identify the automation step and the required selection that is missing, with a clear instruction for resolving it. For example, Run Function could report: "Select a function in the Run Function step before running this automation."
Apply equivalent messages across automation steps that require a selection so users can fix their configuration without inspecting code or contacting support.
Additional context
Reported in this review comment: #19737 (comment)
This is out of scope for PR #19737, which moves Functions into workspace resources. The underlying usability problem affects automation steps generally and should be handled separately.