The error is raised by the Health Cloud managed package AfterUpdate trigger on Account.
It triggers when the running user (the user authenticated in Salesforce Inspector or running a Data Loader/Apex batch job) does not have the Person Account record type enabled on their profile or assigned via permission set, or when the records being updated reference a Person Account record type that is inactive or not deployed in the target sandbox/UAT environment.
Affected users typically run mass updates with API tools in a org using a profile that lacks the Person Account record type.
Customers describe this as: "I'm trying to bulk update person account in our Health Cloud org and the update is failing" and "the person account record type isn't available, contact your administrator."
Cause 1: The running user's profile or permission set does not have the Person Account record type assigned.
1. Identify the user authenticated in your update tool (Salesforce Inspector, Data Loader, or the user running the Apex batch).
2. Go to Setup > Users > Profiles and open that user's profile.
3. In the Account record type section, under Record Type Settings > Account, click [Edit].
4. Move the Person Account record type (for example [PersonAccount]) from Available Record Types to Selected Record Types.
5. Set the Default value to your standard Account record type, then click [Save].
6. If you assign record types by permission set, go to Setup > Permission Sets, open the relevant permission set, select Object Settings > Accounts, and set the Person Account record type Assigned checkbox to checked.
Cause 2: The Person Account record type is inactive or not deployed
1. Go to Setup > Object Manager > Person Account [Account] > Record Types.
2. Confirm the Person Account record type row shows Active = checked. If it is not active, click [Edit], set Active to checked, and click [Save].
Cause 3: Individual records reference a Person Account record type the running user cannot access.
1. In your source CSV, confirm the [RecordTypeId] (or the record type Developer Name) column matches an active Person Account record type the running user has assigned in Cause 1.
2. Remove or correct rows that reference any inactive or unassigned record type.
3. Re-run the bulk update in batches of 200 records to isolate failing rows.
Confirm the issue is resolved by re-running the same Person Account bulk update through Salesforce Inspector against 1 test record; the update completes without the "HealthCloudGA__Account.Trigger: execution of AfterUpdate ... The person account record type isn't available" error, and the record's Last Modified date updates.
005387723

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.