Assign permission set to Automated Process User causing error "CUSTOM_TAB_LIMIT_EXCEEDED"

Question

I'm having trouble assigning a permission set to the Automated Process User. I followed this guide from UnofficialSF, which worked for me before, but for some reason it's not working now for this Org.

I can't find the Automated Process User as usual, in this org it's called Platform Integration User, and there are multiple users with the same name, but I got it because the username is autoproc@00d....

Anyways, when I try to assign the permission set like the guide says,

String automatedProcessUserId = '0057R00.....';
PermissionSet ps = [SELECT Id FROM PermissionSet WHERE Name = 'MyPermissionSetName' LIMIT 1];
insert new PermissionSetAssignment(AssigneeId = automatedProcessUserId, PermissionSetId = ps.Id);

I get this beautiful error:

CUSTOM_TAB_LIMIT_EXCEEDED, Can't complete this operation because it would exceed the number of custom tabs allowed by the user license."

Has anyone else run into this and figured out how to fix it?

Edited:

The requirement for this change is to allow the Automated Process User (or Platform Integration User), to access new Named Credentials when it's executing from a Platform Event Trigger.

Instead of assigning a permission set to the Automated Process User, I changed the running user for the Subscribed Triggers by using the PlatformEventSubscriberConfig metadata element. This will allow the platform event subscriber to access the Named Credentials via the new running user that has the required permissions.

The PlatformEventSubscriberConfig element needs to be created with VSCode and deployed to the target Org, we cannot change this in the setup, and we need the username to exist in the destination Org, so it will not be automatically fixed when deploying from one Sandbox to another.

It's important to take into account that this configuration need to be done in the destination org, also, the user that you are going to use needs to exist in that org.

Answer 1

The actual requirement is to allow the Automated Process User to access new Named Credentials when it's executing from a Platform Event Trigger.

Instead of assigning a permission set to the Automated Process User, I changed the running user for the Subscribed Triggers by using the PlatformEventSubscriberConfig metadata element. This will allow the platform event subscriber to access the Named Credentials via the new running user that has the required permissions.

The PlatformEventSubscriberConfig element needs to be created with VSCode and deployed to the target Org, we cannot change this in the setup, and we need the username to exist in the destination Org, so it will not be automatically fixed when deploying from one Sandbox to another.

It's important to take into account that this configuration need to be done in the destination org, also, the user that you are going to use needs to exist in that org.

To create the file in your VSCode project

1. Create a folder with the path force-app/main/default/platformEventSubscriberConfig
2. Create a file for the PlatformEventSubscriberConfig XML with exactly the same name as you Platform Event Trigger

MyPlatformEventTrigger.platformEventSubscriberConfig-meta.xml

<?xml version="1.0" encoding="UTF-8"?>
<PlatformEventSubscriberConfig xmlns="http://soap.sforce.com/2006/04/metadata">
    <platformEventConsumer>MyPlatformEventTrigger</platformEventConsumer>
    <batchSize>200</batchSize>
    <masterLabel>MyPlatformEventTriggerConfig</masterLabel>
    <user>[email protected]</user>
    <isProtected>false</isProtected>
</PlatformEventSubscriberConfig>

The trigger

trigger MyPlatformEventTrigger on MyPlatformEvent__e(after insert) {
  new MyPlatformEventTriggerHandler().run();
}

Doing this will also allow you to

• Specify the Batch Size for your trigger, default is 2.000
• Executes the trigger with sharing, if you want to enforce sharings for the running user.
• Send Email from the trigger, which is not allowed for the Automated Process

Answer 2

I was encountering the same error, but found that after deleting the Knowledge tab from my org, I was then able to save the permission set assignment without error.

I found a reference to this error in this Salesforce knowledge article that suggested deleting the tab.

After deleting the tab, and assigning the permission set, I was able to recreate the Knowledge tab again without issue.