Frequently Asked Questions (FAQ) about New Agentforce Builder / Agent Script

【Contracts, Licenses, and Migration】

Q. Can I use the new Agentforce Builder in my organization?
A. Available agents vary depending on your contract. If the new Agentforce Builder is not displayed or if an error occurs, please contact your sales representative or technical support.

Related Documentation: Agent Types and Considerations
Related Documentation: Learn About New Agentforce Builder with Agent Script

Q. I want to migrate an Agent created with the classic Agentforce Builder to the new Agentforce Builder / Agentforce Studio / Agent Script.
A. You can easily migrate the classic Agentforce to a new Agentforce Builder Agent with a few clicks. Please refer to this guide first. Some features may not be migratable. Please test the migration process in a Sandbox first.
Note: "topic" has been renamed to "subagent".

Related Documentation: Agentforce Agent Migration Guide

Q. Is it mandatory to write Agent Script in the new Agentforce Builder?
A. No. You can also use "Canvas mode," which allows you to create Agents by clicking and entering instructions in input fields, just like the classic builder.

Related Documentation: Building Agents in Canvas View

【Agent Script & Instructions】

Q. I want to build a new agent using Agent Script, but I don't know how to implement it.
A. There are many implementation example documents and Trailhead modules available for your use.

-Developer Doc: Agentforce Examples
-Trailhead: Build Agents with Agentforce DX
-Help Article: Agent Script
-Trailhead: Programmatic Instructions in Agentforce

Q. How can I develop Agent Script using AI?
A. In addition to using the assistant on the new Agentforce Builder or Agentforce Vibes, you can load the Agent Script documentation, which can be downloaded via the link in this document, into any AI tool of your choice.

Q. I want to output the results of an Agent action in a specific format, but it is displayed in a card format unexpectedly.
A. If you try to "Show in conversation" (is_displayable: True) the result of a standard action as is, it is sometimes difficult to change the output format via instructions. Please try to set "Show in conversation" to off (is_displayable: False), storing it in a variable first, and then writing instructions to output the target variable in your desired format, as this can make the output format more stable.

【Troubleshooting】

Q. I am previewing an Agent in the new Agentforce Builder, but it is not behaving as expected. How do I troubleshoot it?
A. Please refer to the following blog:
Salesforce Developers Blog: Agent Script Decoded – How to debug Agent Script

Q. I am calling a retriever from a prompt template, and although citations were appearing before, they are no longer displaying correctly.
A. You may be able to display citations by following these points:
- In the retriever's "Results" settings, citation settings are enabled.
- In the prompt template settings, the retriever is inserted into the prompt, and "Include Citations" is set to ON in the Format section.
- In the input variables section for the prompt template action, citationMode's is_required is set to True, and description is set to "post_generation".
- In the output variables section for the prompt template action, citations's is_displayable is set to True, and complex_data_type_name is set to @apexClassType/AiCopilot__GenAiCitationOutput.

Note: Creating a custom action in the Asset Library and then adding the action to the Agent is an easier way to configure input variables.

Q. After migrating to the new Agentforce Builder, a compile error occurs in Agent Script, and I cannot save due to "Problems" displayed.
A. Because some specifications are no longer supported in Agent Script, errors may occur even with content that could be saved previously. Click "Problems" at the bottom of the screen to check the error details and location. The main unsupported items and required declarations are as follows:
- linked variables do not support default values.
- list[object] type is not supported.
- Explicit declaration of is_required is required.
Note: If "Problems" does not disappear after fixing the error, please try refreshing your browser tab.

Q. After migrating to the new Agentforce Builder, a "Failed to find source action 'XXX'" error occurs.
A. During the upgrade, the source reference of the action may not have been converted correctly, leaving the action name unfound in the new script. Check if the issue is resolved by the following procedure:
1. Open the Agent Script of the relevant agent in the new builder.
2. Verify that the source value points to a valid action name.
3. Check if the action name displayed in the error message matches the action name defined in the script.
4. If they do not match, manually correct the action name, create a new version, and confirm the version.

Q. CLT (Custom Lightning Types) are not displayed in the Agentforce Builder preview.
A. To display CLT as an output for an agent created in the new Agentforce Builder, please add Enhanced Chat v2 to "Connections" within the new Agentforce Builder.
Additionally, Service Agent and Employee Agent support previews for CLT actions created in the Asset Library. Please create your custom action in the Asset Library first, and then add the action to the agent.
To test and preview actions created within the Agentforce Builder, first activate the version of your Agentforce agent. go to the "Embedded Service Deployment" page, and try "Test Enhanced Web Chat."

-Custom Lightning Type Examples
-Set Up Connections in Agentforce Builder
-Personalize Enhanced Chat v2 Interface with Custom Lightning Types

Q. The new Agentforce Builder returns empty responses with no content.
A. Please try turning off "Display in conversation" (is_displayable: False) for the response and check the behavior.

Q. I want to migrate an Agent created in the new Agentforce Builder to another organization.
A. For agents that have not been activated, you need to migrate the AiAuthoringBundle metadata. For activated agents, you need to migrate the following four components:
- Authoring Bundle Definition Version (AiAuthoringBundle)
- Bot (Bot)
- Bot Version (BotVersion)
- Generative AI Planner Definition (GenAiPlannerBundle)

It is easiest to add the Bot/Bot Version/Generative AI Planner Definition via "Add Dependencies." after adding the Creation Bundle Definition Version. Add other dependent metadata as necessary.

Q. Where can I check the LLM models available in Salesforce and the update content/timing for Agentforce?
A. Currently, Agentforce-related updates are performed asynchronously from the three-times-a-year release cycle, and release content is added to the release notes of the most recent major release (Spring, Summer, Winter). In addition to release notes, the list of supported models is also updated regarding model deprecation and rerouting.

-Ex: Summer '26 release note - Agentforce Platform Features by Month}
-Supported Models
-Prepare for Model Deprecation and Rerouting

【Other】

Q. The issue is not resolved even after checking the FAQ.

A. Please contact support with the following information. Please delete/add content according to your situation.
Subject: <Summary of inquiry>
Description: <Details of inquiry>
Target Org:
Username with login access granted:
Target Agent Name:
Target Agent Topic Name:
Target Agent Action Name:
Target Agent Data Library Name:
Expected Behavior:
Current Behavior:
Reproduction Steps:
Possibility of support representative executing reproduction steps during login access:
Other information if any: