Configure Mail workflow succeeds but SMTP host remains unchanged in Aria Automation Orchestrator

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When executing the Configure mail workflow in VMware Aria Automation Orchestrator, the workflow completes with the message:

Configuration created successfully

However, email workflows or actions continue attempting to connect to the previous SMTP server, resulting in failures such as:

Cannot send mail: 'Couldn't connect to host, port: OldSMTPFQDN, 25; timeout -1' Cause: 'Connection refused'

This issue occurs even after a successful update attempt using the Configure mail workflow.

Environment

VMware Aria Automation Orchestrator 8.x

Cause

The Orchestrator instance contains a Resource element referencing the old SMTP host (e.g., OldSMTPFQDN). This static resource remains bound to the mail configuration or associated workflows, overriding updates made through the Configure mail workflow.

The presence of this outdated configuration prevents the updated SMTP FQDN from being properly applied during workflow execution.

Resolution

To resolve the issue, delete any obsolete SMTP resource objects:

1. Log into Aria Automation Orchestrator.

2. Navigate to Resources.

3. Search for any entries referencing the old SMTP FQDN (e.g., OldSMTPFQDN).

4. Delete these outdated entries.

5. Confirm that a valid entry remains for the new SMTP host.

6. Rerun the Configure mail workflow, if desired.

7. Test email functionality by triggering a workflow that sends an email.