Breaking changes to /beta delete access profile and delete role

What is changing?

The beta endpoints for delete access profile and delete single role are currently asynchronous, meaning that invoking these endpoints will add the task to a queue to be executed later. At the end of March 2023, these endpoints will change to be synchronous, meaning that invoking these endpoints will immediately delete the role or access profile.

These endpoints currently return a 202 response code when successful to indicate that the task has been added to the queue. At the end of March, these endpoints will no longer return a 202. Instead, they will return a 204 to indicate that the role or access profile has immediately been deleted.

When will the change occur?

  • Sandbox will be April 3rd, 2023
  • Production will be a segmented release across the production orgs. The first prod segment will be April 10th, segment 2 will be April 12th, and segment 3 will be April 13th, 2023. To be safe, prepare for your org to be affected on April 10th.

What actions do I need to take?

Please search any code you have written for the use of these two beta endpoints. If you are using them, please confirm if you are explicitly checking for the 202 response in your code. If you are explicitly checking for a 202 response code, you will need to update that code to handle the 204 response code in addition to the 202 response code. You will need to handle both status codes until the change is made to ensure no downtime in your application. Once the change has been made, you can remove the logic to handle the 202 response code.

Please comment on this topic if you have any questions or concerns.

Do we have concrete dates on when these changes are taking place for sandbox and prod?

Engineering has confirmed the schedule:

  • Sandbox will be April 3rd, 2023
  • Production will be a segmented release across the production orgs. The first prod segment will be April 10th, segment 2 will be April 12th, and segment 3 will be April 13th, 2023. To be safe, prepare for your org to be affected on April 10th.