Loading

Email Addresses in Sandbox Appended With '.invalid' After Salesforce Refresh

Дата публикации: Oct 7, 2025
Описание

When you create, refresh, or clone a sandbox, user email addresses are modified in your sandbox so that production users don’t receive automatically generated email messages from the sandbox. User email addresses are appended with ".invalid". This modification ensures that the system ignores these email addresses.

For example, a user's email of atester@universalcontainers.com in production becomes atester@universalcontainers.com.invalid when migrated to a sandbox. If you want the sandbox users to receive automatically generated emails as part of testing, you can correct the email addresses while logged in to the sandbox.

 

Notes:
 

  • The User that initiates the Sandbox refresh will have the same email and password as they have in Production and will receive a notification once the Sandbox refresh is complete.
 
  • If the User who initiates a sandbox clone was manually added as a user in the clone's source sandbox after it was refreshed (i.e. they were not a user in production or automatically copied over when the sandbox was created or refreshed) their user record's email address will also be appended with .invalid, not be notified when the sandbox clone completes, and unable to reset their password. See the Known Issue: User who created sandbox clone has email address altered in resulting clone copy for more details.
 
 
Решение

Sandbox name no longer appended to sandbox User email addresses


In prior releases, sandbox email addresses used the following format 'email@domain.com@example.com.' The suffix prevents emails from being routed externally. Currently, Salesforce no longer uses 'sandbox names' but adds '.invalid' instead.
 


Example

 

  • Sample email: atester@universalcontainers.com

 

  • Previous process for emails when the sandbox is refreshed: atester=universalcontainers.com@example.com

 

  • Current process for emails when the sandbox is refreshed: atester@universalcontainers.com.invalid

 

Why use .invalid?

This modification ensures that the system ignores these email addresses and alleviates unnecessary emails to production users from sandboxes.

 

What is Selective Sandbox Access?

It is possible to provide selective access to a sandbox when creating or refreshing the sandbox. Please see Determine Who Has Sandbox Access and Sandbox Access Considerations for more information.

 

How can we update user email addresses in sandbox after refreshing?

See Change a User email address for more information or you may review Mass update email addresses and usernames.
 


Note: Sandboxes change Salesforce user email addresses on the User Record, but don’t change other email addresses in Salesforce, such as email addresses in contact records.

New and refreshed sandboxes have default email deliverability set to System email only. If you're not receiving expected emails from a sandbox see the 'Email Deliverability' section of the Sandbox Setup Considerations documentation for more details.

To avoid sending unsolicited email from your sandboxes, manually invalidate or delete all email addresses in your sandboxes that don’t belong to users of the sandbox. When testing outbound email, change contact email addresses to the addresses of testers or an automated test script. Please note as of Summer Release 19', Users must have a verified email address and ".invalid" removed from the email address in order to send email alerts via Workflow, Process, Flows or Triggers.
Номер статьи базы знаний

000386507

 
Загрузка
Salesforce Help | Article