Geo-Aware Routing for Agentforce Coworker
Agentforce Coworker follows the same geo-aware routing rules as the broader Agentforce platform for AI inference - the process of running a query through an AI model to generate a response.
Two conditions can route Agentforce Coworker’s inference to US-based infrastructure:
- Your region doesn’t yet have a local deployment for a given model.
- A regional outage or capacity event triggers an automatic fallback.
To disable automatic rerouting to the US for supported models, see Disabling Model Provider Region Fallback at the end of this page.
Agentforce Coworker uses these model components when searching and generating answers. The Routing column shows where each model’s requests go when no local deployment exists or when a fallback triggers. To disable automatic rerouting to the US, see Disabling Model Provider Region Fallback.
| Model | Model ID | Provider | Role in Coworker | Routing |
|---|---|---|---|---|
| Claude Haiku 4.5 | BedrockAnthropicClaude45Haiku | Anthropic on AWS Bedrock | Classifies and routes queries internally within Coworker | See Geo-Aware Routing for Anthropic |
| Claude Sonnet 4.6 | BedrockAnthropicClaude46Sonnet | Anthropic on AWS Bedrock | Synthesizes answers | See Geo-Aware Routing for Anthropic (see Note 1) |
| Amazon Nova Micro | amazon.nova-micro-v1:0 | Anthropic on AWS Bedrock | Improves search ranking | Only used in regions that have this model available locally. See Geo-Aware Routing for Anthropic (see Note 2) |
- Note 1: The Geo-Aware Routing for Anthropic doc only mentions Claude Haiku 4.5. Claude Sonnet 4.6 and Amazon Nova Micro are also Anthropic models on AWS Bedrock and route the same way as Claude Haiku 4.5.
- Note 2: For regions that do not have Amazon Nova Micro being served locally, this model isn’t used.
The Turn Off Model Provider Region Fallback toggle prevents AI requests from being routed to the US when in-region processing is unavailable. When turned on, the feature disables US fallback for Anthropic models only.
Claude Haiku 4.5 and Sonnet 4.6 aren’t available in-region on AWS in Brazil, India, Israel, Korea, Singapore, and Switzerland. Disabling provider region fallback causes requests from those regions to fail. In any region, if both in-region endpoints are overloaded, requests return an error instead of routing to a secondary region. For compliance questions, contact your Salesforce account executive.
- Make sure that Data 360 is turned on. Data 360 is automatically provisioned when a Data 360 license is added to your Salesforce org. See Turn On Data 360.
- From Setup, go to Einstein Setup.
- Turn on Turn Off Model Provider Region Fallback.