Studio Send Email Step Fails: Endpoint Username Does Not Appear to Be Correct
The error Failed to deploy - Failed to apply awares for Out transport '{http://www.capeclear.com/assembly/10}email-out', reason: The endpoint username masked@chegg.com in email out transport id=EmailOut does not appear to be correct
com.capeclear.assembly.AssemblyException: Failed to apply awares for Out transport '{http://www.capeclear.com/assembly/10}email-out', reason: The endpoint username masked@chegg.com in email out transport id=EmailOut does not appear to be correct
What it means
A Studio integration's Send Email step fails to deploy because the out transport's configured username, typically a personal Gmail or other external mailbox address, does not pass the endpoint's validation. This happens at deploy time, before any email is actually sent, so the integration never runs at all.
Troubleshooting
- Open the email-out transport configuration in the assembly and confirm the endpoint username is a fully qualified address with no stray whitespace, quotes, or copy-paste artifacts.
- Confirm the mail provider being targeted actually allows the authentication method configured on the transport. Many personal providers require an app-specific password or OAuth token rather than the account password once two-factor authentication or third-party app access settings are involved.
- Test the same credentials against the mail provider outside of Studio, for example with a basic SMTP client, to confirm the account itself accepts the given username and credential combination.
- Redeploy after correcting either the username format or the authentication method, since the failure happens at deploy validation rather than at runtime send.
⚡ Quick fix
Re-enter the out transport's endpoint username as a clean, fully qualified email address and confirm it matches the authentication method the mail provider actually expects.
✓ Permanent fix
Route Studio outbound email through a dedicated integration mailbox with an app-specific password or OAuth credential set up in advance, rather than a personal consumer email account whose security settings can change and silently break the transport.
Was this helpful?