1

Recently we started facing an error like this

The U#380.1cff (EmailSenderAddress) field can't be updated

I have found the following thread https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000gUKlZ0AW where other customers are complaining about some security upgrade which blocked every pipeline.

Looks like this security update is about blocking change to the EmailSenderAddress but we do not really change it, which is very weird why do we even receive this error.

Deployment failed: four communities failing with the same error The U#380.1cff (EmailSenderAddress) field can't be updated

Currently I have opened a Sev 1 SF Support Case since this blocks our production release tomorrow

Improve this question

1 Answer 1

Reset to default
1

I have investigated a little bit more and created a fresh scratch org not from CI/CD process but manually from the terminal.

Deployed the codebase.

Deployed experience bundle again.

On the second deployment it fails.

Tried to retrieve the network metadata file from the scratch org.

Other users suggested that SF process sets the value of EmailSenderAddress property to the current user email, but in fact it doesn't actually set the email sender address to the current user email but to .invalid suffixed email, even though environment is not a sandbox but a scratch

Git comparison between two network files metadata, the right one having the same appended with .invalid suffix

Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.