Interactive Data Science Service Errors

The Interactive Data Science service is the backend infrastructure for Model Studio, where admins and data scientists create projects, connect data sources, and deploy custom models into Agentforce and Einstein AI features. Errors from this service typically indicate that a project request was invalid or referenced a resource that doesn’t exist, that the org isn’t enabled for the requested capability, or that a platform dependency the service relies on was temporarily unavailable.

The application identifier you supplied doesn’t match a registered application visible to you. Application records are required to resolve project type, data-group affiliation, quota ceilings, and org associations, so any request that depends on an application can’t proceed without one. The request wasn’t processed.

This error occurs when:

• The identifier is incorrect or has a typo.
• The application hasn’t been registered for your org.
• The application was deactivated.
• You’re calling against a different environment from the one the application is registered in.

To resolve this error:

1. List the applications visible to your session and confirm the identifier you’re using.
2. Confirm you’re calling the correct environment.
3. If the application hasn’t been registered for your org, contact your Salesforce admin to register 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: APPLICATION_NOT_FOUND
• The application identifier from the response parameters
• A description of what you were trying to do when the error occurred

You’re authenticated, but you don’t have permission to perform this action. Authorization is enforced by role checks, application-membership checks, environment restrictions, and token validation. The request wasn’t processed.

This error occurs when:

• Your user doesn’t have the role required for the operation.
• Your user doesn’t belong to the application the operation is scoped to.
• The operation is available only in non-production environments and you’re calling it in production.
• Your session token is missing, expired, or couldn’t be parsed.

To resolve this error:

1. Read the response detail — it identifies whether the failure is a missing role, an application membership issue, or an authentication problem.
2. If access should be granted, contact your Salesforce admin to assign the required role or add you to the application.
3. If your token expired, refresh it through your normal authentication flow and retry.
4. If you’re calling a development-only operation, switch to a non-production environment.

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: AUTH_FORBIDDEN
• The required role and actual role from the response parameters
• A description of what you were trying to do when the error occurred

The service couldn’t resolve your org’s identity from the platform’s authentication layer. The failure is usually temporary — retrying often succeeds.

This error occurs when:

• The platform’s authentication layer is briefly unavailable or returning errors.
• A network issue interrupted the connection between services.
• The authentication layer was under heavy load when the call was made.

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 upstream service may be degraded. 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: AUTH_TENANT_RESOLUTION_FAILED
• The approximate time window during which the failures occurred
• A description of what you were trying to do when the error occurred

The service couldn’t authenticate your request. The request is missing valid credentials or the credentials provided couldn’t be verified. The request wasn’t processed.

This error occurs when:

• The authentication header is missing from the request.
• The token in the authentication header is malformed or couldn’t be parsed.
• A secondary token required by the endpoint is missing.
• The token has expired.
• The token signature couldn’t be verified against the expected issuer.

To resolve this error:

1. Confirm your request includes valid authentication credentials.
2. Refresh your token through your normal authentication flow and retry.
3. If the endpoint requires additional credentials, confirm they’re included.
4. If you’re using an SDK, confirm it’s configured for the correct environment — tokens issued for one environment don’t validate in another.

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

A request to the model image registry couldn’t be completed. The failure is usually temporary — retrying often succeeds.

This error occurs when:

• The model image registry is briefly unavailable or returning errors.
• A network issue interrupted the connection.
• The repository or image you referenced doesn’t exist.
• An image policy prevented the operation.

To resolve this error:

1. Wait a few seconds and retry the same request.
2. If you were listing or reading image details, confirm the repository and image tag exist.
3. If you were writing or deleting, check whether the previous attempt applied before retrying.

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: AWS_ECR_FAILURE
• The operation and error code from the response parameters
• A description of what you were trying to do when the error occurred

A request to the file storage layer couldn’t be completed. The failure is usually temporary — retrying often succeeds.

This error occurs when:

• The file storage layer is briefly unavailable or returning errors.
• A network issue interrupted the connection.
• The file system or storage task you referenced is in a state that doesn’t yet allow the operation (for example, still being created or updated).
• A platform capacity limit was reached.

To resolve this error:

1. Wait a few seconds and retry the same request.
2. If you were reading storage information, the request is safe to retry.
3. If you were modifying storage (resize, attach, detach), check the current state before retrying to avoid applying the operation twice.

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: AWS_FSX_FAILURE
• The operation and error code from the response parameters
• A description of what you were trying to do when the error occurred

A request to the AI training infrastructure couldn’t be completed. The failure is usually temporary — retrying often succeeds.

This error occurs when:

• The AI training infrastructure is briefly unavailable or returning errors.
• A network issue interrupted the connection.
• The resource you referenced is in a state that doesn’t yet allow the operation (for example, still being created, updated, or deleted).
• A platform capacity limit was reached.

To resolve this error:

1. Wait a few seconds and retry the same request.
2. If you were reading resource status, the request is safe to retry.
3. If you were modifying a resource (deleting an endpoint, stopping a notebook), check its current state before retrying to avoid applying the operation twice.
4. If the error indicates a capacity limit was reached, contact your Salesforce admin.

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: AWS_SAGEMAKER_FAILURE
• The operation and error code from the response parameters
• A description of what you were trying to do when the error occurred

A file storage operation failed while uploading, downloading, or generating a secure access link for a file. The failure is usually temporary — retrying often succeeds.

This error occurs when:

• The file storage service is briefly unavailable.
• A network issue interrupted the transfer.
• The file you referenced no longer exists or has expired.
• The service received an empty response where a file record or access link was expected.

To resolve this error:

1. Wait a few seconds and retry the same request.
2. If you were uploading, retry from the beginning rather than resuming a partial transfer.
3. If you were downloading, confirm the file still exists — secure access links are time-limited.

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: BLOB_STORAGE_FAILURE
• The operation from the response parameters
• A description of what you were trying to do when the error occurred

The application’s data-group affiliation is missing the required service classification tag. Without it, the service can’t generate the data sources needed to create the project. The request wasn’t processed.

This error occurs when:

• The application was registered without a data-group affiliation.
• The data-group affiliation exists but doesn’t include the required tag, or the tag is empty.
• The application identifier points to an application configured for a different deployment.

To resolve this error:

1. Confirm the application identifier in the request is correct.
2. Verify the application’s data-group affiliation includes the required service classification tag. Contact your Salesforce admin if you can’t view or update it.
3. After the configuration is updated, resubmit the project creation 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: CLOUD_TAG_MISSING
• The application identifier from the request
• A description of what you were trying to do when the error occurred

A request to Data 360 couldn’t be completed. The failure is usually temporary — retrying often succeeds.

This error occurs when:

• Data 360 is briefly unavailable or returning errors.
• A network issue interrupted the connection.
• A query timed out.
• A query result exceeded a size limit.

To resolve this error:

1. Wait a few seconds and retry the same request.
2. If the failed call was a query, narrow the scope (smaller time range or fewer rows) and retry.
3. If the failed call was a write, retry with the same data — a temporary failure doesn’t partially apply changes.

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: DATACLOUD_FAILURE
• The operation from the response parameters
• A description of what you were trying to do when the error occurred

The data source’s org doesn’t match the project’s org configuration. A data source can only be attached to a project whose org list includes the data source’s org. The request wasn’t processed.

This error occurs when:

• A multi-org project doesn’t include the data source’s org in its org list.
• A single-org data source is being attached to a project owned by a different org.
• A data source identifier from one project is being supplied to an update on a different project.

To resolve this error:

1. Compare the data source org and the project org list shown in the response parameters.
2. If the data source belongs in this project, add its org to the project’s org list and resubmit.
3. If the project’s org list is correct, choose a data source owned by one of the project’s orgs instead.
4. If you’re updating a data source, confirm the identifier belongs to a data source already attached to this project.

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: DATASOURCE_TENANT_MISMATCH
• The data source org and project org list from the response parameters
• A description of what you were trying to do when the error occurred

The data source type you supplied isn’t allowed for this application. The response includes the value you sent and the list of allowed values. The request wasn’t processed.

This error occurs when:

• The data source type doesn’t match any allowed types for the application.
• The data source entity isn’t in the application’s allowed entity list.
• For Einstein Search data sources, the request is missing required fields or includes a configuration not permitted in production.

To resolve this error:

1. Read the response detail — it names the value you supplied and the list of allowed values.
2. Choose a type or entity from the allowed list and resubmit.
3. For Einstein Search data sources, confirm the request includes both an index identifier and a non-empty access policies list. In production environments, only read access is permitted.
4. If you believe the application should allow the value you sent, contact your Salesforce admin to review the application’s 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: DATASOURCE_TYPE_INVALID
• The supplied type and allowed types from the response parameters
• A description of what you were trying to do when the error occurred

A platform service the request depended on didn’t respond in time. The failure is usually temporary — retrying often succeeds.

This error occurs when:

• A downstream service is briefly slow or under heavy load.
• A network slowdown interrupted the connection.
• A specific operation required more time than allowed.

To resolve this error:

1. Wait a few seconds and retry the same request.
2. If the operation was large or complex, try a smaller or simpler version and retry.
3. If timeouts continue across multiple attempts, 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: DOWNSTREAM_TIMEOUT
• A description of what you were trying to do when 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: 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

A request to the platform’s compute infrastructure couldn’t be completed. The failure is usually temporary — retrying often succeeds.

This error occurs when:

• The platform’s compute infrastructure is briefly unavailable or returning errors.
• A network issue interrupted the connection.
• A platform policy prevented the operation.
• The infrastructure was rate-limiting when the call was made.

To resolve this error:

1. Wait a few seconds and retry the same request.
2. If this happened while checking a resource’s status, the request is safe to retry.
3. If this happened while starting, stopping, or modifying a resource, check its current state before retrying to avoid applying the operation twice.

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

The service couldn’t get a response from the LLM gateway. The failure is usually temporary — retrying often succeeds.

This error occurs when:

• The LLM gateway is briefly unavailable or returning errors.
• The gateway returned a malformed response.
• The model you requested is overloaded or rate-limited.
• Your request exceeded a gateway limit.

To resolve this error:

1. Wait a few seconds and retry the same request.
2. If retries continue to fail, try a smaller request.
3. If your configuration supports multiple model options, try a different one.

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: LLM_GATEWAY_FAILURE
• The operation and error code from the response parameters
• A description of what you were trying to do when the error occurred

The service couldn’t complete a database operation. The failure is usually temporary — retrying often succeeds. This isn’t a problem with your request.

This error occurs when:

• The database is briefly unavailable or under heavy load.
• A database operation timed out.
• A network issue interrupted the connection to the database.

To resolve this error:

1. Wait a few seconds and retry the same request.
2. If you were reading data, the request is safe to retry.
3. If you were writing data, check the current state of the affected resource after retrying — the previous attempt may or may not have committed.

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

The project operation you requested isn’t allowed from the project’s current status. The response includes the current status and the list of allowed transitions. The request wasn’t processed.

This error occurs when:

• The project is already in the target state or past it.
• The project is in an APPROVED, REVOKED, or other terminal state and you tried to update it or its data sources — only projects in UNAPPROVED status accept updates.
• You tried to create an environment for a project that hasn’t been approved yet.
• You tried to clone a project that isn’t in APPROVED status.
• Another operation changed the project’s status between when you read it and when you submitted this request.

To resolve this error:

1. Refresh the project to see its current status.
2. Review the allowedTransitions list in the response — it lists the valid next states from the current status.
3. Choose a transition from allowedTransitions and retry. If the project is in a terminal state, create a new project instead.
4. To update a project or its data sources, verify the project is in UNAPPROVED status first.
5. To clone a project, verify it’s in APPROVED status first.

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: PROJECT_INVALID_TRANSITION
• The from-status, to-status, and allowed transitions from the response parameters
• A description of what you were trying to do when 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: PROJECT_STATE_UPDATE_FAILED
• 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 combination of project type and application identifier in your request isn’t allowed. The request wasn’t processed.

This error occurs when:

• A Data Exploration application was paired with a non-DATA_EXPLORATION project type, or vice versa.
• The application identifier is correct but it doesn’t support the project type you want.
• The application’s supported project types were updated after the request was prepared.

To resolve this error:

1. Confirm the application identifier you’re using.
2. If the application is a Data Exploration application, set the project type to DATA_EXPLORATION. If it isn’t, use PROTOTYPING or DEBUGGING.
3. If you believe the application should support the type you sent, contact your Salesforce admin to review the application’s 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: PROJECT_TYPE_INVALID
• The project type and application identifier from the response parameters
• A description of what you were trying to do when the error occurred

The quota you requested for an application exceeds the ceiling configured for that application type. This is a hard limit, not a temporary rate window. Retrying with the same value won’t help. The request wasn’t processed.

This error occurs when:

• The requested quota value is greater than the ceiling for the application type.
• The application type’s ceiling was lowered since you last set the quota.

To resolve this error:

1. Compare the requested value against the ceiling — both are in the response parameters.
2. Lower the requested value to at or below the ceiling and resubmit.
3. If you need a quota above the ceiling, contact your Salesforce admin. Raising the ceiling for an application type is a policy decision that may require approvals.

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: QUOTA_EXCEEDED
• The quota name, requested value, and ceiling from the response parameters
• A description of what you were trying to do when 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: REGISTRY_CONFIG_INVALID
• 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 request you submitted didn’t pass validation. The response includes details about the specific field, value, or rule that failed. The request wasn’t processed.

This error occurs when:

• A required field is missing from the request, or required parameters aren’t included for the operation.
• An identifier in the path or body isn’t a valid UUID.
• A field uses a value outside the allowed set.
• A resource value (CPU, GPU, or memory) is negative.
• An image version is deprecated or isn’t supported in your deployment environment.
• The requester isn’t in the project’s authorized users list, or the approver is also the project creator (which isn’t permitted outside development environments).

To resolve this error:

1. Read the response detail — it names the specific field or rule that failed and the rejected value.
2. Correct the listed field and resubmit.
3. If a project access rule failed (authorized users list, approver-equals-creator), adjust project membership or have a different user perform the action.

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: REQUEST_VALIDATION_FAILED
• A redacted copy of the request you submitted
• A description of what you were trying to do when the error occurred

The resource you requested doesn’t exist or isn’t visible to you. The request wasn’t processed.

This error occurs when:

• The identifier in the request is incorrect or has a typo.
• The resource was deleted or deactivated after you obtained the identifier.
• The resource belongs to a different org or environment and isn’t visible to your session.
• You don’t have permission to view this resource. The service returns a not-found response rather than a permission error to avoid disclosing whether the resource exists.
• A platform-managed resource (such as a notebook or training job) has already completed or been cleaned up.

To resolve this error:

1. List the resources of the relevant type to confirm the identifier is current before using it.
2. Confirm you’re calling the correct environment — identifiers don’t carry over between environments.
3. If the resource was created very recently, wait a few seconds and retry.
4. If you’re confident the identifier is correct and the resource should be visible to you, contact your Salesforce admin to confirm your org and permissions.

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: RESOURCE_NOT_FOUND
• The resource type and identifier from the response parameters
• A description of what you were trying to do when the error occurred

The service couldn’t complete a permissions lookup because the platform’s identity and access management layer was unavailable. The failure is usually temporary — retrying often succeeds.

This error occurs when:

• The platform’s identity and access management layer is briefly unavailable or returning errors.
• A network issue interrupted the connection.
• A service error prevented the permission lookup from completing.

To resolve this error:

1. Wait a few seconds and retry the same request.
2. If the error continues, 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: SEC_IAM_FAILURE
• The operation from the response parameters
• A description of what you were trying to do when the error occurred

A notification couldn’t be delivered. This is a temporary failure in the notification path — the underlying operation you performed wasn’t affected. Retrying the original operation isn’t necessary.

This error occurs when:

• The notification delivery service is briefly unavailable.
• The destination channel was archived or renamed.
• A network issue interrupted the delivery.

To resolve this error:

1. Wait a few seconds and retry if the notification is required.
2. Confirm the destination channel is still active and configured to accept messages.
3. If the notification isn’t critical, it’s safe to proceed — the underlying operation completed successfully.

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

Your org hasn’t been registered for the application you’re calling against. Operations that depend on the org-application association can’t proceed until registration is complete. The request wasn’t processed.

This error occurs when:

• The org hasn’t been registered for this application.
• The org identifier in the request doesn’t match the application’s registered orgs.
• The application’s registration was removed.

To resolve this error:

1. Confirm the org identifier in the request is the org you intend to manage.
2. If the org isn’t registered, contact your Salesforce admin to register it for this application.
3. After the org is registered, retry 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: TENANT_NOT_REGISTERED
• The org identifier and application identifier from the response parameters
• A description of what you were trying to do when the error occurred

Your org has opted out of data sharing for the capability you’re trying to use. This is an org-level policy controlled by your administrator. Requests that depend on this capability are blocked until the opt-out is reversed. The request wasn’t processed.

This error occurs when:

• The org administrator has opted the org out of data sharing.
• An org-wide policy refresh changed the opt-out status.
• A prototyping project is being created or updated for an opted-out org — prototyping doesn’t allow exceptions to the opt-out policy.

To resolve this error:

1. Read the response detail. If it mentions a prototyping restriction, the exception path isn’t available — either use a different project type or have the org opt back in.
2. Contact your Salesforce admin to opt the org back in to data sharing.
3. After the opt-out is reversed, retry 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: TENANT_OPTED_OUT
• The capability and org identifier from the response parameters
• A description of what you were trying to do when the error occurred

The interactive streaming session ended unexpectedly. The session can be re-established — retrying often succeeds.

This error occurs when:

• The underlying compute environment closed the stream.
• Your authentication credentials expired during the session.
• The network connection between your client and the service was interrupted.
• The session exceeded an idle timeout and was closed.

To resolve this error:

1. Wait a few seconds, then reconnect and start a new session.
2. If your credentials expired, refresh them before reconnecting.
3. Any commands that were in progress when the session closed should be reissued in the new session.
4. If reconnects fail repeatedly, the underlying environment may not be available — try a different environment if one is configured.

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: WEBSOCKET_SESSION_FAILURE
• The session state from the response parameters
• A description of what you were trying to do when the error occurred

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