A failed profile save now tells you what it did save

Renaming your organisation touches two places: the name your team signs in against, and the copy the platform reads everywhere else. Saving the rest of your profile — legal name, support address, website, timezone, region, fiscal year — is a third step.

Until now, if one of those steps failed after an earlier one had already gone through, the save reported a flat error. The rename might have stuck, or not, and nothing on screen said which. The same was true for Sustentus staff editing a profile on your behalf.

Now each of those failures says what happened:

• The rename went through, the rest did not. The name is already correct everywhere. Save the other fields again — you do not need to retype the name.
• The rename reached your sign-in organisation but not the platform. The old name is still what everyone sees, and nothing else changed. Save again to finish it.

A save that works, and a rename your sign-in provider refuses outright, behave exactly as before — the refusal still leaves everything untouched.