We've seen Salesforce returning an unknown error with GACK code 435681881 around the time of the Winter ‘26 release (v65) when trying to retrieve the problematic agent using the GenAIPlannerBundle metadata type like the example below:
$ sf project retrieve start -m GenAiPlannerBundle:Agent_for_Setup
Error (UNKNOWN_EXCEPTION): UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 1625230720-93690 (435681881)
Trying to retrieve all agents succeeds, but with a warning. Curiously, the agent with the warning (Agent_for_Setup) is partly retrieved, having only planner action schemas, and no agent XML:
$ sf project retrieve start -m GenAiPlannerBundle
Warning:
Metadata API received improper input. Please ensure file name and capitalization is correct.
Load of metadata from db failed for metadata of type:GenAiPlannerBundle and file name:Agent_for_Setup.
We can see that the agent exists in Salesforce, which allows us to delete the agent from there. However, deleting the agent in Salesforce is a nuclear option and doesn’t get us any closer to a working fixed agent.
Alternatively, attempting to delete the agent via the Salesforce CLI fails without providing an error message:
$ sf project delete source -m GenAiPlannerBundle:Agent_for_Setup
Status: Failed
How can we identify and fix the problem if using source control?
If using source control, we might have the agent XML from before problem occurred.
This is useful because we can try to find out which part of the XML caused the issue.
Example of the XML before the error occurred:
First, we can try deploying the agent in place, but we find that the deployment fails, again without Salesforce providing an error message:
$ sf project deploy start -m GenAiPlannerBundle:Agent_for_Setup
Status: Failed
Then we can try to deploy the metadata as a new agent, by changing the filename of the agent. This still fails, however, at least we are provided with an error message:
$ sf project deploy start -m GenAiPlannerBundle:Test_Agent
Function not found: null
This gives us a clue that there is a bad function, which could either be one of the genAiFunctions or a function referenced within one of the genAiPlugins.
Lately, Salesforce have also been providing a line and column number of the bad function, which makes it easier to identify and remove.
We also know from experience with debugging Agentforce issues that certain functions have been deprecated by Salesforce, so they can be safely removed and may fix the issue like the ones below:
AdminCopilot__ObjectManagementAdminCopilot__UserAccessManagementFlowAgentforce__AutomationFlowsTopicEmployeeCopilot__GeneralCRMAdminCopilot__FallbackTopic
Example of the XML with the function we removed:
The agent could then be successfully deployed:
$ sf project deploy start -m GenAiPlannerBundle:Agent_for_Setup
Status: Succeeded
How can we identify and fix the problem if NOT using source control?
If you don’t have access to the original metadata, because source control hasn’t been used, and the exception makes it impossible to retrieve the XML, we can make use of available Salesforce APIs to list and delete the referenced GenAiPlannerFunctionDef records.
First, find out the ID for the agent:
$ sf org list metadata -m GenAiPlannerBundle
┌───────────────────────────────┬────────────────────┐
│ Full Name │ Id │
├───────────────────────────────┼────────────────────┤
│ ... │ ... │
│ Agent_for_Setup. │ 16jN20000000QQjIAM │
│ ... │ ... │
└───────────────────────────────┴────────────────────┘
Then, use that ID to query for GenAiPlannerFunctionDef records:
$ sf data query -q
"SELECT Id, Plugin FROM GenAiPlannerFunctionDef
WHERE PlannerId = '16jN20000000QQjIAM'"
┌────────────────────┬───────────────────────────────────────────────┐
│ ID │ PLUGIN │
├────────────────────┼───────────────────────────────────────────────┤
│ 17DN200000A1JsYMAV │ IdentityCopilot__ExternalClientAppManagement │
│ 17DN200000A1JsZMAV │ AdminCopilot__FallbackTopic │
│ 17DN200000A1JsaMAF │ IdentityCopilot__ConnectedAppMigration │
│ 17DN200000A1JsbMAF │ AdminCopilot__ObjectManagement │
│ 17DN200000A1JscMAF │ AdminCopilot__UserAccessManagement │
│ 17DN200000A1JsdMAF │ IdentityCopilot__ConnectedAppSummarize │
│ 17DN200000BLetlMAD │ 172N2000000PuNBIA0 │
│ 17DN200000D4UCwMAN │ EmployeeCopilot__AnswerQuestionsWithKnowledge │
└────────────────────┴───────────────────────────────────────────────┘
We know from before that AdminCopilot__ObjectManagement and AdminCopilot__UserAccessManagement are deprecated, so we can go ahead and delete them using SOQL:
$ sf data delete record --sobject GenAiPlannerFunctionDef
--record-id 17DN200000A1JsbMAF
Deleting Record... Success
$ sf data delete record --sobject GenAiPlannerFunctionDef
--record-id 17DN200000A1JscMAF
Deleting Record... Success
Note: if none of the advice above works in your case, we would suggest you get in touch with Salesforce Support. They will be able to dig into the error logs on their side and let you know which functions are causing the corruption in the agent.