ML Lake Service Errors

The ML Lake service manages data storage access for Einstein AI pipeline jobs. Errors from this service typically indicate that the request or org identifier was invalid, that credentials couldn’t be issued or aren’t authorized, or that the service was temporarily unavailable.

MLLAKE_USER_FORBIDDEN 

You were authenticated, but the identity you’re calling with isn’t permitted to perform the requested operation on the target org or namespace. Retrying without changing permissions won’t succeed. The request wasn’t processed.

This error occurs when:

  • The calling identity doesn’t have the required permission for the target org or namespace.
  • The caller’s org doesn’t match the org in the request.
  • The namespace has a stricter access policy that hasn’t been granted to the caller.
  • A required entitlement isn’t enabled for your org.

How to Troubleshoot 

To resolve this error:

  1. Contact your Salesforce admin to confirm the calling identity has the required permission for the target org and namespace.
  2. If the caller is acting across orgs, confirm the tenant in the request matches an org the caller is authorized for.

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: MLLAKE_USER_FORBIDDEN
  • The tenant and namespace values from the request
  • A description of what you were trying to do when the error occurred

MLLAKE_USER_INTERNAL_ERROR 

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: MLLAKE_USER_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

MLLAKE_USER_INVALID_REQUEST 

The request you sent couldn’t be parsed, or it contained an identifier the service doesn’t accept. The request was rejected before any processing began. The request wasn’t processed.

This error occurs when:

  • The request body wasn’t valid JSON.
  • A required field was missing or had an unexpected type.
  • An identifier in the body was malformed.
  • The Content-Type header wasn’t set to application/json.

How to Troubleshoot 

To resolve this error:

  1. Confirm the request body is well-formed JSON.
  2. Check that the required fields (namespace, tenant) are present and contain string values.
  3. Confirm the Content-Type header is application/json.

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: MLLAKE_USER_INVALID_REQUEST
  • A redacted copy of the request body and Content-Type header you sent

MLLAKE_USER_SERVICE_UNAVAILABLE 

The ML Lake service is temporarily unable to handle your request. The failure isn’t specific to your input. The request wasn’t processed, but retrying often succeeds.

This error occurs when:

  • The service is restarting or a deployment is in progress.
  • A platform dependency the service relies on is temporarily unavailable.
  • The service is under heavy load.

How to Troubleshoot 

To resolve this error:

  1. Wait a few seconds and retry the same request.
  2. If the error continues for more than a few minutes, the service may be in an active incident. Check trust.salesforce.com for known incidents.

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: MLLAKE_USER_SERVICE_UNAVAILABLE
  • The approximate time window during which the failures occurred

MLLAKE_USER_TEMPORARY_FAILURE 

The ML Lake service couldn’t complete your request because the platform’s data tokenization layer didn’t return a token. Your request was valid — the failure is on the dependency side. Retrying often succeeds.

This error occurs when:

  • The platform’s data tokenization layer is briefly unavailable or restarting.
  • A network issue interrupted the connection between services.
  • The data tokenization layer was under temporary resource pressure.

How to Troubleshoot 

To resolve this error:

  1. Wait a few seconds and retry the same request.
  2. If the error continues for more than a few minutes, check trust.salesforce.com for known incidents.

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: MLLAKE_USER_TEMPORARY_FAILURE
  • The approximate time window during which the failures occurred

MLLAKE_USER_TENANT_VALIDATION_FAILED 

The tenant or namespace value in your request didn’t pass validation. The request was understood but rejected because one of those values wasn’t in an acceptable form. The request wasn’t processed.

This error occurs when:

  • The tenant value didn’t match the expected format or contained invalid characters.
  • The namespace value contained characters that aren’t allowed — only lowercase letters, digits, and hyphens are accepted.
  • The tenant or namespace exceeded the maximum allowed length.
  • The tenant value didn’t match the org context associated with your credentials.

How to Troubleshoot 

To resolve this error:

  1. Check the tenant value and confirm it matches the expected format.
  2. Confirm the namespace uses only lowercase letters, digits, and hyphens, and is within the length limit.
  3. If your credentials are bound to a specific org, confirm the tenant in the request body matches that org — or omit the field and let the service infer it.

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: MLLAKE_USER_TENANT_VALIDATION_FAILED
  • A description of what you were trying to do when the error occurred

MLLAKE_USER_UNAUTHENTICATED 

The ML Lake service couldn’t verify your identity. The request was rejected before any processing began because the credentials you provided were missing, malformed, or expired. The request wasn’t processed.

This error occurs when:

  • The Authorization header was missing from the request.
  • The token in the Authorization header was expired or revoked.
  • The token was issued for a different environment or audience than the one you called.
  • The Authorization header used an unsupported scheme.

How to Troubleshoot 

To resolve this error:

  1. Confirm the request includes a valid Authorization header.
  2. Refresh your token and retry.
  3. Confirm the token was issued for the same environment (sandbox, production) and audience as the endpoint you’re calling.
  4. If you’re proxying requests through another service, confirm that service is forwarding the Authorization header unchanged.

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: MLLAKE_USER_UNAUTHENTICATED
  • A description of what you were trying to do when the error occurred

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