Einstein Compute Service Errors

The Einstein Compute service schedules and runs AI model training and data processing jobs that power Agentforce and other generative AI features. Errors from this service typically indicate that a job request was invalid or referenced a resource that doesn’t exist, that the platform’s compute infrastructure was temporarily unavailable or at capacity, or that an internal dependency encountered an unexpected failure.

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

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: CCP_AOP_INSTRUMENTATION_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 platform’s authentication layer failed to respond to the service’s request. The job can’t start until the authentication layer is available again. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• The platform’s authentication layer is temporarily overloaded or restarting.
• A temporary network issue is preventing the service from reaching the authentication layer.

To resolve this error:

1. Wait a moment and try again.
2. 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: CCP_AUTH_SERVICE_FAILED
• What you were doing when the error occurred

The compute backend is at capacity with running jobs and can’t accept this request right now. Waiting about a minute and trying again usually works.

This error occurs when:

• The backend has reached its maximum number of concurrent jobs.
• The system is handling a high volume of requests.

To resolve this error:

1. Wait about a minute and try again.
2. If this happens consistently, consider spreading job submissions over a longer window.

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: CCP_BACKEND_BUSY
• What you were trying to do and how often the error occurs

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

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: CCP_BACKEND_HEALTH_CHECK_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 compute backend required to run your job is temporarily unavailable. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• The backend is restarting or undergoing maintenance.
• A temporary infrastructure issue is preventing the backend from accepting requests.

To resolve this error:

1. Wait a moment and try again.
2. 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: CCP_BACKEND_NOT_AVAILABLE
• What you were doing when the error occurred

The compute backend referenced in your request doesn’t exist in this environment. Retrying won’t help until the backend identifier is corrected.

This error occurs when:

• The backend identifier is incorrect or contains a typo.
• The backend was removed or renamed.
• The backend isn’t available in your org’s environment.

To resolve this error:

1. Verify the backend identifier is correct.
2. Confirm the backend is available in your 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: CCP_BACKEND_NOT_FOUND
• The backend identifier you specified

The compute backend configuration in your request failed validation. Retrying with the same request won’t help.

This error occurs when:

• Required fields are missing or contain invalid values.
• Field values don’t meet the backend’s validation constraints.

To resolve this error:

1. Review the error response for specific validation failures.
2. Correct the configuration and resubmit 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: CCP_BACKEND_VALIDATION_FAILED
• 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: CCP_CHAOS_TESTING_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 job classification referenced in your request doesn’t exist. Retrying won’t help until the classification is corrected.

This error occurs when:

• The classification identifier is misspelled or uses the wrong casing.
• The classification has been removed or is no longer supported.
• The classification isn’t available in your org’s environment.

To resolve this error:

1. Verify the classification identifier is correct.
2. Check the API documentation for supported classifications.
3. Update your request to use a valid classification identifier.

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: CCP_CLASSIFICATION_NOT_FOUND
• The classification identifier you specified

The platform’s credential provisioning step timed out before completing. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• Platform authentication services are under high load.
• A temporary network delay is slowing down the credential provisioning process.

To resolve this error:

1. Wait a few seconds and try again.
2. 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: CCP_CREDENTIAL_MINTING_TIMEOUT
• What you were doing when the error occurred

The Data 360 tenant identifier in your request is invalid. Retrying won’t help until the identifier is corrected.

This error occurs when:

• The tenant identifier is missing, malformed, or contains invalid characters.
• The tenant identifier references a tenant that doesn’t exist or is no longer active.

To resolve this error:

1. Verify the tenant identifier format matches the expected pattern.
2. Confirm the tenant exists and is active in Data 360.
3. Correct the tenant identifier and resubmit 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: CCP_D360_INVALID_TENANT
• What you were trying to do when the error occurred

Your request to the platform’s credential management layer contained invalid parameters. Retrying with the same request won’t help.

This error occurs when:

• Required fields are missing or contain incorrect data types.
• The request body doesn’t match the expected format.

To resolve this error:

1. Review the error response for specific validation failures.
2. Correct the invalid parameters and 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: CCP_DAAS_SERVICE_BAD_REQUEST
• What you were trying to do when the error occurred

The platform’s credential management layer is temporarily unavailable. Trying again usually succeeds.

This error occurs when:

• The credential management layer is under heavy load or restarting.
• A temporary network issue is preventing the service from reaching its dependency.

To resolve this error:

1. Wait a moment and try again.
2. 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: CCP_DAAS_SERVICE_FAILED
• What you were doing when the error occurred

The service can’t connect to its database. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• The database is restarting or briefly unavailable.
• A temporary network issue is preventing the service from reaching its database.

To resolve this error:

1. Wait a moment and try again.
2. 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: CCP_DATABASE_CONNECTION_FAILED
• What you were doing when the error occurred

The service encountered an internal database error while processing your request. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• A temporary database issue caused the query to fail.
• The service is experiencing elevated load.

To resolve this error:

1. Wait a few seconds and try again.
2. 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: CCP_DATABASE_QUERY_FAILED
• What you were doing when the error occurred

A database query took longer than the allowed time and was stopped. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• The database is under elevated load.
• A temporary query performance issue caused the timeout.

To resolve this error:

1. Wait a few seconds and try again.
2. 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: CCP_DATABASE_QUERY_TIMEOUT
• What you were doing 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: CCP_DATABASE_TRANSACTION_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

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: CCP_DRIVER_POD_NOT_FOUND
• 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

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

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

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: CCP_INVALID_BACKEND_CONFIG
• 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 backend type specified in your request isn’t valid. Retrying won’t help until the backend type is corrected.

This error occurs when:

• The backend type value is missing, malformed, or not recognized by the service.
• The backend type isn’t supported in your org’s configuration.

To resolve this error:

1. Review the valid backend types in the API documentation.
2. Confirm the backend type is supported in your environment.
3. Correct the backend type and resubmit 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: CCP_INVALID_BACKEND_TYPE
• The backend type value you specified

The external job identifier in your request is invalid. Retrying won’t help until the identifier is corrected.

This error occurs when:

• The identifier is malformed or contains invalid characters.
• The identifier doesn’t match the expected format.

To resolve this error:

1. Verify the external job identifier matches the expected format.
2. Correct the identifier and resubmit 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: CCP_INVALID_EXTERNAL_JOB_ID
• What you were trying to do when the error occurred

The job request failed validation. Retrying with the same request won’t help.

This error occurs when:

• The request body is malformed or contains invalid JSON.
• Required fields contain incorrect data types or values outside the allowed range.
• Fields don’t pass the service’s validation rules.

To resolve this error:

1. Review the error response for specific validation failures.
2. Check the API documentation for the correct request format.
3. Correct the invalid fields and resubmit.

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: CCP_INVALID_JOB_REQUEST
• What you were trying to do when the error occurred

The job specification in your request failed validation. Retrying won’t help until the specification is corrected.

This error occurs when:

• The job specification is malformed or missing required fields.
• Field values in the specification don’t meet validation constraints.

To resolve this error:

1. Review the error response for specific validation failures.
2. Check the job specification format in the API documentation.
3. Correct the invalid fields and resubmit.

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: CCP_INVALID_JOB_SPEC
• 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: CCP_INVALID_KUBERNETES_CONFIG
• 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

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: CCP_INVALID_REDIS_CONFIG
• 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 data processing application configuration in your request failed validation. Retrying won’t help until the configuration is corrected.

This error occurs when:

• The application configuration is missing required fields or contains invalid values.
• Dependencies aren’t correctly specified in the configuration.

To resolve this error:

1. Review the application configuration against the API documentation.
2. Ensure all required fields are present and correctly formatted.
3. Correct the configuration and resubmit.

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: CCP_INVALID_SPARK_APPLICATION
• 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: CCP_INVALID_TEMPORAL_CONFIG
• 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 service is at maximum capacity and can’t accept new jobs right now. Waiting about a minute and trying again usually works.

This error occurs when:

• Too many jobs are currently running or queued.
• The system’s job capacity limit has been reached.

To resolve this error:

1. Wait about a minute and try again.
2. If this happens frequently, consider spreading job submissions over a longer time window.

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: CCP_JOB_AT_CAPACITY
• What you were trying to do and how often the error occurs

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: CCP_JOB_KILL_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 job referenced in your request doesn’t exist. Retrying won’t help until the job identifier is corrected.

This error occurs when:

• The job identifier is incorrect or contains a typo.
• The job was deleted or expired before this request was made.
• The request is targeting the wrong org or environment.

To resolve this error:

1. Verify the job identifier is correct.
2. Confirm the job hasn’t been deleted or expired.
3. Ensure you’re querying the correct org and 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: CCP_JOB_NOT_FOUND
• The job identifier you specified

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: CCP_JOB_PAYLOAD_SERIALIZATION_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 service can’t retrieve job status right now due to a temporary platform issue. Trying again usually succeeds.

This error occurs when:

• An upstream service dependency is temporarily unavailable.
• A temporary network issue is preventing the service from checking job status.

To resolve this error:

1. Wait a moment and try again.
2. 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: CCP_JOB_STATUS_QUERY_FAILED
• What you were doing 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: CCP_JOB_SUBMISSION_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

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

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: CCP_JSON_SERIALIZATION_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 service couldn’t publish an event to the platform’s internal messaging layer. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• The internal messaging layer is temporarily unavailable or under high load.
• A temporary network issue is preventing the publish operation.

To resolve this error:

1. Wait a moment and try again.
2. 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: CCP_KAFKA_PUBLISH_FAILED
• What you were doing when the error occurred

A call to the platform’s compute infrastructure timed out. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• The platform’s compute infrastructure is under elevated load.
• A temporary network delay caused the timeout.

To resolve this error:

1. Wait a few seconds and try again.
2. 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: CCP_KUBERNETES_API_TIMEOUT
• What you were doing when the error occurred

Your request to the platform’s compute infrastructure contained invalid or malformed data. Retrying won’t help until the issue is corrected.

This error occurs when:

• The request is missing required fields or contains invalid values.
• The request doesn’t meet the expected format for this operation.

To resolve this error:

1. Review the error response for specific validation failures.
2. Check the API documentation for the correct request format.
3. Correct the request and resubmit.

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: CCP_KUBERNETES_CLIENT_ERROR
• 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: CCP_KUBERNETES_CLIENT_INIT_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 platform’s compute infrastructure returned an error. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• The compute infrastructure is temporarily overloaded or restarting.
• A temporary network issue is affecting compute operations.

To resolve this error:

1. Wait a moment and try again.
2. 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: CCP_KUBERNETES_SERVER_ERROR
• What you were doing 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: CCP_LEAD_MANAGEMENT_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

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

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

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

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: CCP_MISSING_CONFIGURATION
• 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

Your request is missing a required field. The Einstein Compute service can’t process the request without all required fields. Retrying won’t help until the missing field is included.

This error occurs when:

• A required field was omitted from the request body or parameters.
• An empty or null value was provided for a field that requires a value.

To resolve this error:

1. Review the error response to identify which field is missing.
2. Check the API documentation for the endpoint’s required fields.
3. Add the missing field with a valid value and retry.

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: CCP_MISSING_REQUIRED_FIELD
• What you were trying to do when the error occurred

No compute backend matching your request was found in this environment. Retrying won’t help until the backend configuration is corrected.

This error occurs when:

• The backend with the specified type or name doesn’t exist.
• The backend has been removed or renamed.
• The backend isn’t available in your org’s environment.

To resolve this error:

1. Verify the backend identifier is correct.
2. Confirm the backend is available in your environment.
3. If a specific backend isn’t required, try using the default backend.

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: CCP_NO_BACKEND_FOUND
• The backend identifier or type you specified

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: CCP_OUTBOX_EVENT_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 service encountered a temporary error forwarding an internal event. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• The internal event relay is temporarily unavailable.
• A temporary platform issue prevented the event from being forwarded.

To resolve this error:

1. Wait a moment and try again.
2. 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: CCP_OUTBOX_RELAY_FAILED
• What you were doing when the error occurred

A call to the platform’s compute layer timed out. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• The platform’s compute layer is under elevated load.
• A temporary network delay caused the timeout.

To resolve this error:

1. Wait a few seconds and try again.
2. 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: CCP_RAY_API_TIMEOUT
• What you were doing when the error occurred

Your request to the platform’s compute layer contained invalid or malformed data. Retrying won’t help until the issue is corrected.

This error occurs when:

• The request is missing required fields or contains invalid values.
• The request doesn’t meet the expected format.

To resolve this error:

1. Review the error response for specific validation failures.
2. Check the API documentation for the correct request format.
3. Correct the request and resubmit.

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: CCP_RAY_CLIENT_ERROR
• What you were trying to do when the error occurred

The platform’s compute layer returned an error. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• The compute layer is temporarily overloaded or restarting.
• A temporary network issue is affecting compute operations.

To resolve this error:

1. Wait a moment and try again.
2. 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: CCP_RAY_SERVER_ERROR
• What you were doing 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: CCP_REBALANCING_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 service encountered a temporary problem while processing your job. The platform retries automatically. If you still see this error, trying again usually succeeds.

This error occurs when:

• A required service was temporarily unavailable during job processing.
• A temporary network or timeout issue occurred while submitting or checking job status.

To resolve this error:

1. Wait a moment and try again.
2. 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: CCP_RECOVERABLE_JOB_ERROR
• What you were doing when the error occurred

The service can’t connect to the platform’s caching layer. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• The caching layer is temporarily restarting or unavailable.
• A temporary network issue is preventing the connection.

To resolve this error:

1. Wait a moment and try again.
2. 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: CCP_REDIS_CONNECTION_FAILED
• What you were doing 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: CCP_REDIS_LOCK_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

An operation on the platform’s caching layer timed out. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• The caching layer is under elevated load.
• A temporary network delay caused the timeout.

To resolve this error:

1. Wait a few seconds and try again.
2. 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: CCP_REDIS_OPERATION_TIMEOUT
• What you were doing 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: CCP_REDIS_STREAM_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

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

A data processing application with the same identifier already exists. Retrying won’t help until the conflict is resolved.

This error occurs when:

• You’re trying to register an application that already exists in this environment.
• The application identifier isn’t unique.

To resolve this error:

1. Check whether an application with this identifier already exists.
2. Use a different identifier or update the existing application instead of creating a new 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: CCP_SPARK_APPLICATION_ALREADY_EXISTS
• The application identifier you specified

The data processing application referenced in your request doesn’t exist. Retrying won’t help until the identifier is corrected.

This error occurs when:

• The application identifier is incorrect or contains a typo.
• The application was removed.

To resolve this error:

1. Verify the application identifier is correct.
2. Confirm the application hasn’t been removed.
3. Correct the identifier and resubmit.

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: CCP_SPARK_APPLICATION_NOT_FOUND
• The application identifier you specified

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

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

An internal stream processing error occurred. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• A temporary internal processing error prevented the stream operation from completing.
• The service is experiencing elevated load.

To resolve this error:

1. Wait a few seconds and try again.
2. 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: CCP_STREAM_PROCESSING_FAILED
• What you were doing 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: CCP_STREAM_TRIM_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

Your request to the platform’s authentication token service contained invalid parameters. Retrying won’t help until the parameters are corrected.

This error occurs when:

• Required fields are missing or incorrectly formatted in the token request.
• The requested permissions don’t match what’s allowed for your service.
• Token request parameters contain invalid values.

To resolve this error:

1. Review the error response for specific validation failures.
2. Verify all required fields are present and correctly formatted.
3. Correct the parameters and resubmit.

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: CCP_STS_TOKEN_BAD_REQUEST
• What you were trying to do when the error occurred

The platform’s authentication token service is temporarily unavailable. Trying again usually succeeds.

This error occurs when:

• The authentication token service is under heavy load or restarting.
• A temporary network issue is preventing token generation.

To resolve this error:

1. Wait a moment and try again.
2. 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: CCP_STS_TOKEN_GENERATION_FAILED
• What you were doing 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: CCP_TEMPORAL_WORKFLOW_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

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: CCP_TEMPORAL_WORKFLOW_TIMEOUT
• 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 compute backend type you specified isn’t supported. Retrying won’t help until you switch to a supported backend type.

This error occurs when:

• The backend type isn’t available in this service version or your org’s configuration.
• The backend type has been deprecated or isn’t enabled for your environment.

To resolve this error:

1. Check the API documentation for supported backend types.
2. Update your request to use a supported backend type.

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: CCP_UNSUPPORTED_BACKEND
• The backend type you specified

The platform’s secrets management layer failed to retrieve a required configuration. This is usually a temporary issue. Trying again usually succeeds.

This error occurs when:

• The secrets management layer is temporarily unavailable or under high load.
• A temporary network issue is preventing the service from retrieving the configuration.

To resolve this error:

1. Wait a moment and try again.
2. 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: CCP_VAULT_FETCH_FAILED
• What you were doing when the error occurred

The secrets management configuration in your request is invalid or incomplete. Retrying won’t help until the configuration is corrected.

This error occurs when:

• Required configuration fields are missing or contain invalid values.
• The path or namespace format doesn’t match what’s expected.
• The authentication method specification doesn’t match the configured setup.

To resolve this error:

1. Review the error response for specific validation failures.
2. Verify all configuration fields are present and correctly formatted.
3. Correct the configuration and resubmit.

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: CCP_VAULT_INVALID_CONFIG
• What you were trying to do when the error occurred

The path or field referenced in your request doesn’t exist in the platform’s secrets management layer. Retrying won’t help until the reference is corrected.

This error occurs when:

• The path doesn’t exist or has been removed.
• The field name is misspelled or doesn’t exist at the specified path.
• The secret was relocated.

To resolve this error:

1. Verify the path and field name are correct.
2. Confirm the secret exists and hasn’t been relocated or removed.
3. Correct the reference and resubmit.

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: CCP_VAULT_PATH_OR_FIELD_NOT_FOUND
• What you were trying to do when the error occurred

The request doesn’t have permission to access the specified path in the platform’s secrets management layer. Retrying won’t help until the permissions issue is resolved.

This error occurs when:

• The credentials used for this request don’t have access to the requested path.
• The path is restricted to specific roles or services.
• The authentication credentials have insufficient privileges.

To resolve this error:

1. Verify that your org’s configuration has the necessary access permissions for this operation.

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: CCP_VAULT_UNAUTHORIZED_PATH
• 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

Agent Service Reasoner Errors

Agentforce Data Library Service Errors

Authentication Service Errors

Bring Your Own Node Service Errors

Einstein Compute Service Errors

General Agentforce Service Errors

Interactive Data Science Service Errors

Language Detection Service Errors

ML Lake Service Errors

Model Builder Errors

Prediction Service Errors

Models and Prompts

Headless Agentforce Development