If your Salesforce org has been upgraded to Summer '25 (64) and you use source control to manage Agentforce metadata, you may notice unexpected changes or missing metadata during comparisons in Gearset. This is due to a change introduced by Salesforce: GenAiPlanner has been replaced with a new metadata type, GenAiPlannerBundle.
This guide explains what this change means, how you can resolve comparison mismatches, and how to migrate the metadata stored in Git to match the new format.
What’s changed in Summer '25?
Salesforce has introduced a new metadata type:
API Version | Metadata Type |
v60 - v63 |
|
v64+ |
|
While both metadata types describe an Agentforce Agent and its topics, they differ in structure and how they’re stored in your project.
Gearset supports both types, but mismatches can occur when the metadata type in your Git repository isn't supported by the API version used in your comparison.
How to migrate metadata in Git using Gearset
If your repository still contains the old GenAiPlanner type, you’ll need to convert it to the GenAiPlannerBundle type to avoid false Deleted differences when comparing or deploying using v64 of the Metadata API:
Git branch containing Spring '25 (63) GenAiPlanner metadata
To update your repository using Gearset:
Run an
On-demand comparisonwith yourSummer '25 (64)org as the source, and your chosen Git branch as the target.Select
Summer '25 (64)as the API version in your metadata filter.
Filter by the
Agent planner bundleandAgent plannermetadata types.Select the
Agent plannermetadata you want to delete, and the corresponding newAgent planner bundlemetadata to deploy in its place.Deploy to your Git branch.
Comparing a Summer '25 (64) Agentforce org with a Spring '25 (63) Git branch
Your repository structure will now match Salesforce’s expectations for Agentforce deployments using Summer '25 (64) comparisons:
Git branch containing Summer '25 (64) GenAiPlannerBundle metadata
What about org-to-org deployments?
When moving metadata directly between Salesforce orgs, API version mismatches can produce some odd results when retrieving and deploying Agentforce metadata.
Spring '25 (63) Comparisons
Salesforce orgs on Summer '25 (64) are backwards compatible with Spring '25 (63). GenAiPlannerBundle metadata can be retrieved or deployed as GenAiPlanner metadata.
Org Version (Source/Target) | v63 | v64 |
v63 | GenAiPlanner | GenAiPlanner |
v64 | GenAiPlanner | GenAiPlanner |
Summer '25 (64) Comparisons
Salesforce orgs on Spring '25 (63) cannot be compared when specifying Summer '25 (64) for comparisons. Only GenAiPlannerBundle metadata can be retrieved or deployed on Summer '25 (64) orgs when using this API version.
Org Version (Source/Target) | v63 | v64 |
v63 | Not supported* | Not supported |
v64 | Not supported* | GenAiPlannerBundle |
* Unknown type name 'GenAiPlannerBundle' specified in package.xml
Still need help?
If you’re unsure about what metadata format you’re using, or you’re seeing unexpected results in Gearset comparisons, reach out to our team using the in-app chat — we’re always happy to help.