One of our production org has been automatically migrated to Spring22 by Salesforce last week-end

The following jobs has been run by SF platform during the update (audit trail extract)

enter image description here

After this upgrade, all of the permission set has been automatically updated:

  • For some of them, all fieldAccess has been removed (Standard and Custom fields)
  • For some of them, only some fieldAccess has been removed (again standard and/or custom fields)

All Permission Sets, even the ones not in our CI, even Salesforce Internal ones, has been automatically updated, it can not be from a manual operation

enter image description here

  • Has anyone observed the same error on his/her production org after Spring22 update ?

  • Is there some "one-click" way to rollback the forced destruction of rights on PS ?

  • What do the permission sets' Last Modified By say? Feb 7, 2022 at 17:38
  • 1
    Updated in december, so it can not be a manual update or a deployment :/ Feb 7, 2022 at 17:41

1 Answer 1


If you are not maintaining any backup of these then I am afraid it wont be possible. You can still raise a ticket with salesforce and check it.

  • I luckily have metadata backups of this org (that's how I tracked the origin of the update: same day than Spring22 upgrade) , but I work at a Salesforce Integrator company and i'd like to know i t can happen on any of the many many orgs we maintain :/ Feb 7, 2022 at 17:42
  • 3
    I think you should raise a case with Salesforce to find out what really happened, and to let the wider community know what you are told since this seems really worrying to me.
    – Phil W
    Feb 7, 2022 at 20:58

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .