Language Detection Service Errors

The language detection service identifies the language of text submitted through Agentforce and Einstein AI features. Errors from this service typically indicate that the input text was too short or the wrong type, that required parameters were missing, or that the pipeline configuration connecting language detection to other steps was incorrect.

Language detection couldn’t complete because a required internal step didn’t produce the expected result. This is a platform-internal condition and isn’t caused by your Agentforce configuration. The request wasn’t processed.

This error occurs when:

• An internal platform condition prevented the language detection service from completing the request.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: DEPENDENCY_RESULT_NOT_FOUND
• The approximate time the error occurred

The text sent to the language detection step is too short for the service to identify a language reliably. The service needs at least the minimum number of characters shown in the error message to produce a confident result. The request wasn’t processed.

This error occurs when:

• The upstream step or variable that feeds the language detection step produced text shorter than the minimum length.
• Whitespace or punctuation was trimmed and the remaining content fell below the minimum.
• The language detection step is receiving an empty or near-empty value from its input mapping.

To resolve this error:

1. In Agentforce Builder, open the subagent or agent action that runs the language detection step.
2. Trace the input variable that feeds the step’s text field and confirm it produces text of at least the required length.
3. If short inputs are expected in your flow, add a length check earlier and route them around the language detection step.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: INPUT_TEXT_BELOW_MINIMUM
• The name of the subagent or agent action that contains the language detection step

This error code indicates an unexpected system error and not an issue with your configuration. If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: LDS_INTERNAL_ERROR
• Any context that might help with the investigation, such as when the error occurred, what you or your end user were doing at the time, and whether you’re able to reproduce it

The language detection service couldn’t complete the analysis. The request format was valid, but a temporary internal issue prevented the service from producing a result. The same input often succeeds on a second attempt.

This error occurs when:

• A temporary issue arose inside the language detection engine while processing the input.
• Temporary resource pressure affected the service.

To resolve this error:

1. Wait a moment and try again. This issue is usually temporary.
2. If the error persists across multiple attempts, note the trace ID and contact Salesforce Customer Support.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: LDS_LINGUA_PROCESSING_ERROR
• Whether the error repeated across multiple attempts

Language detection couldn’t complete because an internal step produced an unexpected result. This is a platform-internal condition and isn’t caused by your Agentforce configuration. The request wasn’t processed.

This error occurs when:

• An internal platform condition prevented the language detection service from completing the request.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: MULTIPLE_DEPENDENCY_RESULTS
• The approximate time the error occurred

Language detection couldn’t complete because an internal step in the service didn’t produce output. This is a platform-internal condition and isn’t caused by your Agentforce configuration. The request wasn’t processed.

This error occurs when:

• An internal platform condition prevented the language detection service from completing the request.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: NO_DEPENDENCIES_FOUND
• The approximate time the error occurred

This error code indicates an unexpected system error and not an issue with your configuration. If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: POSTPROCESSOR_INTERNAL_ERROR
• Any context that might help with the investigation, such as when the error occurred, what you or your end user were doing at the time, and whether you’re able to reproduce it

The language detection step ran without the input text it needs. The service requires text to analyze, and it couldn’t find a text input from the step’s configuration or from an upstream step in the flow. The request wasn’t processed.

This error occurs when:

• The language detection step’s text input isn’t mapped to a variable or upstream output.
• The variable mapped to the text input resolves to an empty or missing value at runtime.
• An upstream step expected to supply the text either didn’t run or produced no output.

To resolve this error:

1. In Agentforce Builder, open the language detection step’s configuration.
2. Confirm the text input is mapped to a variable or the output of an upstream step.
3. If the text comes from an upstream step, verify that step runs before the language detection step and produces a value.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: REQUIRED_PARAMS_MISSING
• The name of the subagent or agent action that contains the language detection step

The language detection step received a value that isn’t text. Language detection only works with text data, so the request couldn’t be processed. This is typically caused by an upstream step or integration producing the wrong data type. The request wasn’t processed.

This error occurs when:

• An upstream step or integration produced a non-text value where text was expected.

To resolve this error:

1. Note the trace ID and the time the error occurred.
2. Contact Salesforce Customer Support to investigate the source of the non-text input.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: TEXT_MUST_BE_STRING
• The approximate time the error occurred
• The name of the subagent or agent action that contains the language detection step

The confidence threshold configured on the language detection step is outside the allowed range. The threshold controls how confident the service must be before returning a language match. Valid values are between 0 and 1 inclusive. The request wasn’t processed.

This error occurs when:

• The confidence threshold field on the language detection step is set to a negative number or a value greater than 1.
• A percentage value (for example, 50) was entered instead of a decimal (for example, 0.5).
• A variable used to set the confidence threshold at runtime resolves to a value outside the [0, 1] range.

To resolve this error:

1. In Agentforce Builder, open the language detection step’s configuration.
2. Set the confidence threshold to a decimal value between 0 and 1 (for example, 0.5, not 50).
3. If the confidence threshold is set from a variable, confirm the variable’s source produces values in the [0, 1] range.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: THRESHOLD_OUT_OF_RANGE
• The confidence threshold value that was configured

j

Get Started

Agentforce Examples

Agent Script

Agentforce DX

Agentforce APIs and SDKs

Agentforce Actions

Agentforce Service Errors

Language Detection Service Errors

Agent Service Reasoner Errors

Authentication Service Errors

Model Builder Errors

Interactive Data Science Service Errors

ML Lake Service Errors

Models and Prompts

Headless Agentforce Development