---
schema_version: "1"
id: 8862587c3e63018b7c7a0e595a4a88225cc6b19501d3a4c0c869f666878c6312
title: Considerations and Limitations in Multi-Agent Solutions
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ai/264-0-0/agent_multi_orch_consider.md
canonical_url: https://help.salesforce.com/s/articleView?id=ai.agent_multi_orch_consider.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f88497bd72e6be2362a3a38b4c4763f9a2098f9252fae00361dda0002cee16f2
description: Review these considerations and limitations for Multi-Agent Orchestration for Agentforce.
products:
  - Agentforce
  - Cross Cloud
release: "264"
---
# Considerations and Limitations in Multi-Agent Solutions

Review these considerations and limitations for Multi-Agent Orchestration for Agentforce.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions. <a href="https://help.salesforce.com/s/articleView?id=ai.agent_setup_explore_types.htm&amp;release=264.0.0&amp;type=5" title="Learn about agent types and default templates for specific clouds and common use cases.">Required add-on licenses vary by agent type.</a></td></tr></tbody></table>

- You can connect agents as subagents within a single Salesforce org. Multi-agent orchestration isn't currently supported for Agentforce agents:
    - across multiple Salesforce orgs
    - with external, non-Agentforce agents
- You can use these agent type combinations for orchestrator agents and connected subagents:
    - Agentforce Service Agent (ASA) orchestrator agent with ASA connected subagents
    - Agentforce Employee Agent (AEA) orchestrator agent with AEA connected subagents
    - AEA orchestrator agent with ASA connected subagentsFor an ASA orchestrator agent, users aren’t propagated to AEA connected subagents.
- File-based agents (for example, SDR or Analytics) aren't supported in this release.
- Multi-agent Orchestration users are required to:
    - Activate new agent versions to be available as connected subagents.
    - Update scripts to use handoff mode. See "Orchestrator Agent Routing to Connected Subagents" in [Agent Script in Multi-Agent Solutions](https://help.salesforce.com/s/articleView?id=ai.agent_multi_orch_script.htm&release=264.0.0&type=5 "Implement determinism in your multi-agent solution by using Agent Script and these design patterns.").
- Connect only active agents to your orchestrator agent. Don’t select an inactive agent.
- Both orchestrator agents and connected subagents can escalate to a human representative. See "Escalate to a Human Representative" in [Agent Script in Multi-Agent Solutions](https://help.salesforce.com/s/articleView?id=ai.agent_multi_orch_script.htm&release=264.0.0&type=5 "Implement determinism in your multi-agent solution by using Agent Script and these design patterns.").
- This release supports one level of delegation from an orchestrator agent to connected subagents.
- Timeout limits:
    - For orchestrator agents: 120 seconds. The timeout includes the elapsed time spent by the orchestrator agent doing specialized work, such as delegating to connected subagents and synthesizing the results.
    - For the connected subagents: 30 seconds.The orchestrator agent synthesizes timeout errors.
- Agentforce Voice isn’t a supported configuration for this release of Multi-Agent Orchestration for Agentforce. However, you're welcome to experiment with the understanding that it's unsupported.
- For this release, we support both context variables and custom variables. We support variable mapping in one direction only: from an orchestrator agent to connected subagents.
- Currently, you can't deactivate a connected subagent.
- For customers who didn't participate in the Multi-Agent Orchestration for Agentforce (Pilot) program, before using an agent with Multi-Agent Orchestration for Agentforce:
    - If the agent was built with the new Agent Builder, create and activate a new version of it.
    - If the agent was built with the legacy Agentforce Builder, upgrade it to the new Agent Builder. See [Upgrade an Agent from the Legacy Builder to the New Builder](https://help.salesforce.com/s/articleView?id=ai.agent_setup_create_upgrade.htm&release=264.0.0&type=5 "Create a new version of an agent from the legacy Agentforce Builder in Setup in the new Agentforce Builder in Agentforce Studio, with just a few clicks. The new version contains all of the original agent's subagents, actions, system messages and settings, data, and connections, converted to Agent Script. Upgrading an agent doesn't affect the original agent in the legacy builder. You can continue to access and edit the agent in the legacy builder.").