-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Action - Send customized email
-
Severity 3 - Minor
Issue Summary
When an automation rule contains multiple Send email actions and is relatively large/complex, the Customized prefix option within the Send email component may not load before rule validation runs. This results in a validation error and prevents the rule from being enabled. Manually opening/clicking the Send email component causes the option to load, after which the validation error disappears and the rule can be saved.
Steps to Reproduce
- Create a relatively large/complex automation rule containing multiple Send email actions.
- Configure the Send email actions to use the Customized prefix option.
- Attempt to save and enable the automation rule without manually opening/clicking the Send email components.
- Observe the validation behavior.
- Open/click the affected Send email component manually.
- Attempt to save the rule again.
Expected Results
- All Send email component options, including Customized prefix, should load before validation is performed.
- The rule should validate successfully and be saved without requiring the user to manually open or interact with the Send email components.
Actual Results
- The Customized prefix option does not initially load for the Send email component.
- Validation runs before the component has finished loading the required option.
- The rule fails validation and cannot be saved.
- Manually clicking/opening the Send email component causes the Customized prefix option to load, after which the validation error disappears and the rule can be saved.
Workaround
Manually open/click each affected Send email component before saving the rule. This forces the component and the Customized prefix option to load, allowing the validation to complete successfully and the rule to be saved.