Authentication Service Errors

The Agentforce authentication service manages org provisioning and the credentials that allow Agentforce and Einstein AI features to operate. Errors from this service typically indicate that an org couldn’t be provisioned, that authentication credentials couldn’t be validated, or that a platform dependency the service relies on was temporarily unavailable.

You don’t have permission to perform this operation. The request was rejected because the required role or scope isn’t granted.

This error occurs when:

  • The credential doesn’t include the permissions needed for this operation.
  • Your role was changed and no longer grants access to this resource.
  • The request targets a resource restricted to a different set of callers.
  • Required authorization scopes are missing from the credential.

To resolve this error:

  1. Verify the credential includes the roles or scopes required for this operation.
  2. If your role was changed recently, confirm the updated role still grants the required access.
  3. Contact your Salesforce admin if you believe access should be permitted.

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: ACCESS_DENIED
  • A description of the resource or operation you were trying to access

The authentication token service policy for this request is invalid. It may contain duplicate entries. The authentication service can’t evaluate the policy as supplied.

This error occurs when:

  • The policy contains duplicate statements or identity entries.
  • The policy structure doesn’t match the expected format.

To resolve this error:

  1. Remove any duplicate entries from the policy.
  2. Review the policy structure for errors and correct them.

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

The authentication token service policy referenced in this request doesn’t exist. The authentication service can’t evaluate the policy until a valid one is specified.

This error occurs when:

  • The policy name or identifier is incorrect or mistyped.
  • The policy hasn’t been created yet.
  • The policy was deleted.

To resolve this error:

  1. Verify the policy name or identifier is correct.
  2. Confirm the policy exists. List available policies if needed.
  3. If the policy should exist but doesn’t, create it 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: ACCESS_POLICY_NOT_FOUND
  • A description of what you were trying to do when the error occurred

The authentication service couldn’t obtain a required access token from a platform dependency. This is a temporary issue. Wait a moment and try again.

This error occurs when:

  • A platform dependency is temporarily unavailable or undergoing maintenance.
  • A temporary network issue is preventing the service from reaching the token endpoint.
  • The dependency is reducing capacity under high load.

To resolve this error:

  1. Wait at least 30 seconds and try again. This is a temporary error that usually clears on its own.
  2. If the error persists after several retries, check trust.salesforce.com for known incidents.
  3. If you’re sending a high volume of requests, reduce the number of concurrent requests.

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

The API key you provided was rejected. Agentforce couldn’t authenticate your request because the key is incorrect, has been revoked, or was issued for a different service.

This error occurs when:

  • The API key is mistyped, truncated, or includes extra whitespace.
  • The API key has been revoked or rotated.
  • The key was issued for a different service or environment.

To resolve this error:

  1. Confirm the API key is correct and copied without modifications.
  2. Rotate or re-issue the API key if it’s been revoked.
  3. Verify the key is valid for the service and environment you’re using.

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

Agentforce couldn’t authenticate the request. The credentials or client identity sent with it were missing, malformed, or not accepted. For security reasons, the error doesn’t say which check failed.

This error occurs when:

  • The token or credential is missing, malformed, or expired.
  • The token was issued for a different service or tenant.
  • Agentforce couldn’t verify the client identity sent with the request.
  • Required identity information is missing from the request.
  • The request reached the service through an unsupported route.

To resolve this error:

  1. Get a new token or credential, and send the request again with it.
  2. Confirm the token was issued for the tenant and service you’re calling.
  3. Send the request through the supported endpoint for your integration.

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

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: AUTHENTICATION_MISCONFIGURED
  • 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 integration layer is temporarily unavailable. The authentication service can’t complete the request until it recovers. This is usually a temporary issue. Wait a moment and try again.

This error occurs when:

  • The platform’s integration layer is temporarily unavailable or undergoing maintenance.
  • A temporary network issue is preventing the authentication service from reaching it.
  • The integration layer is reducing capacity under high load.

To resolve this error:

  1. Wait at least 30 seconds and try again. This is a temporary error that usually clears on its own.
  2. If the error persists after several retries, check trust.salesforce.com for known incidents.
  3. If you’re sending a high volume of requests, reduce the number of concurrent requests.

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

The application name in the request doesn’t match the application the credentials were issued for. The authentication service can’t process the request because the application context is inconsistent.

This error occurs when:

  • The application name in the request differs from the application the caller is registered as.

To resolve this error:

  1. Confirm the application name matches the application your credentials were issued for.
  2. Send the request with that application’s credentials.

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

The platform couldn’t complete org provisioning because an internal dependency is temporarily unavailable. This is distinct from a provisioning failure caused by a business rule conflict. It indicates that a platform service the provisioning workflow depends on couldn’t be reached. This is usually a temporary issue.

This error occurs when:

  • A platform dependency is temporarily unavailable or undergoing maintenance.
  • A temporary network issue is preventing the platform from completing the provisioning workflow.
  • The dependency is reducing capacity under high load.

To resolve this error:

  1. Wait at least 30 seconds and try again. This is a temporary error that usually clears on its own.
  2. If the error persists after several retries, check trust.salesforce.com for known incidents.
  3. If you’re sending a high volume of requests, reduce the number of concurrent requests.

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

Agentforce couldn’t complete the cross-cloud trust operation because a service it depends on returned an error. This issue is usually temporary.

This error occurs when:

  • A service that Agentforce depends on is temporarily unavailable or returned an error.
  • A short-lived capacity or connectivity problem occurred.

To resolve this error:

  1. Wait 30 seconds and try again.
  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: CROSS_CLOUD_TRUST_FAILED
  • The time you first saw the error

The request would violate a data integrity constraint (for example, a uniqueness rule or a reference to a related record that doesn’t exist). The authentication service can’t complete the operation as submitted.

This error occurs when:

  • You’re trying to create a record with an identifier that already exists.
  • The request references a related record that doesn’t exist.
  • You’re trying to delete a record that still has dependent records attached.

To resolve this error:

  1. Check whether a record with the same identifier already exists before retrying.
  2. Confirm all referenced records exist before creating relationships between them.
  3. Remove or reassign dependent records before attempting to delete a parent record.

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: DATA_INTEGRITY_VIOLATION
  • A description of the operation you were attempting when the error occurred

The authentication service couldn’t connect to its database. This is a temporary infrastructure issue. Wait a moment and try again.

This error occurs when:

  • The database is temporarily unavailable or undergoing maintenance.
  • A temporary network issue is preventing the service from reaching the database.
  • The database is recovering from a failover.

To resolve this error:

  1. Wait at least 30 seconds and try again. This is a temporary error that usually clears on its own.
  2. If the error persists after several retries, 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: DB_CONNECTION_FAILURE
  • A description of what you were trying to do when the error occurred

A database query took too long to complete. This is a temporary issue. Wait a moment and try again.

This error occurs when:

  • The database is under high load.
  • A query is taking longer than usual due to temporary resource contention.

To resolve this error:

  1. Wait at least 30 seconds and try again. This is a temporary error that usually clears on its own.
  2. If the error persists after several retries, 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: DB_QUERY_TIMEOUT
  • A description of what you were trying to do when the error occurred

A service that this request depends on is temporarily unavailable. Some operations might be slower or fail until it recovers. This issue is usually temporary.

This error occurs when:

  • A service that Agentforce depends on is restarting, failing over, or under maintenance.
  • A short-lived network or capacity problem occurred.

To resolve this error:

  1. Wait 30 seconds and try again.
  2. Expect slower responses while the service recovers.
  3. 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: DEPENDENCY_UNAVAILABLE
  • The time you first saw the error

Agentforce couldn’t find the tenant that the request refers to, so the request can’t be processed.

This error occurs when:

  • The tenant identifier is incorrect.
  • The tenant hasn’t been provisioned or was removed.

To resolve this error:

  1. Confirm the tenant identifier in the request is correct.
  2. Confirm the tenant has been provisioned.

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: EXTERNAL_TENANT_NOT_FOUND
  • The tenant identifier you used

The feature you’re trying to use isn’t recognized by the authentication service. The request can’t proceed until the feature name is correct and the feature is enabled for your org.

This error occurs when:

  • The feature name is mistyped or uses an outdated identifier.
  • The feature hasn’t been enabled for this environment or org.
  • The request was sent to the wrong region or environment.

To resolve this error:

  1. Verify the feature name matches the name registered with the authentication service.
  2. Confirm the feature is enabled in the target environment.
  3. If the feature should be registered, contact your Salesforce admin to verify the 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: FEATURE_NOT_FOUND
  • A description of what you were trying to do when the error occurred

The authentication service’s request to the platform’s identity directory timed out. This is a temporary issue. Wait a moment and try again.

This error occurs when:

  • The platform’s identity directory is experiencing high load or slow response times.
  • A temporary network issue is causing latency.
  • The identity directory is undergoing maintenance.

To resolve this error:

  1. Wait at least 30 seconds and try again. This is a temporary error that usually clears on its own.
  2. If the error persists after several retries, check trust.salesforce.com for known incidents.
  3. If you’re sending a high volume of requests, reduce the number of concurrent requests.

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

The platform’s identity directory is temporarily unavailable. The authentication service can’t resolve the lookup until it recovers. This is usually a temporary issue. Wait a moment and try again.

This error occurs when:

  • The platform’s identity directory is temporarily unavailable or undergoing maintenance.
  • A temporary network issue is preventing the authentication service from reaching it.
  • The identity directory is reducing capacity under high load.

To resolve this error:

  1. Wait at least 30 seconds and try again. This is a temporary error that usually clears on its own.
  2. If the error persists after several retries, check trust.salesforce.com for known incidents.
  3. If you’re sending a high volume of requests, reduce the number of concurrent requests.

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

The access token you provided isn’t valid. It may have expired, been revoked by an administrator, or been issued for a different service.

This error occurs when:

  • The token has expired.
  • The token was revoked or invalidated by an administrator.
  • The token was issued for a different audience or environment.

To resolve this error:

  1. Refresh the access token using your refresh credential.
  2. Confirm the token’s audience matches the service you’re calling.
  3. Re-authenticate if refresh fails or the token has been revoked.

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

The role ARN provided for the assume-role operation is invalid or incorrectly formatted. The authentication service can’t process the request until the ARN is corrected.

This error occurs when:

  • The ARN format doesn’t match the expected pattern.
  • The ARN contains invalid characters, typos, or extra whitespace.
  • The ARN refers to a resource type other than a role.

To resolve this error:

  1. Verify the ARN follows the correct format for a role ARN.
  2. Check for any typos, extra characters, or leading and trailing spaces.
  3. Confirm the ARN refers to a role, not another resource 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: INVALID_ASSUME_ROLE_ARN
  • A description of what you were trying to do when the error occurred

The authentication context attached to the request isn’t valid for this operation. The platform can’t authorize the call without a correct authentication context.

This error occurs when:

  • The context is missing required fields.
  • The context references an org, identity, or scope that doesn’t match the credential.
  • The context was built from stale data after an org or identity change.

To resolve this error:

  1. Refresh the authentication context from the source of truth.
  2. Confirm the context’s org, identity, and scope match the credential being used.
  3. Verify all required context fields are populated.

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

The platform couldn’t complete an internal service handshake because a credential key is invalid or expired. The key needs to be rotated or refreshed before the request can succeed.

This error occurs when:

  • The credential key has expired and needs to be rotated.
  • The key value was truncated or copied incorrectly.
  • The key was issued for a different environment or service.

To resolve this error:

  1. If you manage the credential key, rotate or refresh it.
  2. Confirm the key value is transmitted exactly as issued.
  3. Verify the key was issued for the correct environment and service.

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

The core tenant GUID in your request isn’t in the expected format. Agentforce can’t process the request until the GUID is valid.

This error occurs when:

  • The GUID isn’t in standard UUID format.
  • The GUID contains invalid characters or extra spaces.
  • The GUID is incomplete or truncated.
  • A different type of identifier was used in place of the core tenant GUID.

To resolve this error:

  1. Confirm the GUID follows the standard format, such as xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.
  2. Remove any invalid characters, and trim leading or trailing spaces.
  3. Confirm you’re using the core tenant GUID and not a different tenant 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: INVALID_CORE_TENANT_GUID_FORMAT
  • The format of the GUID you used, with the actual values masked

Agentforce doesn’t recognize the feature name in your request. The request can’t be processed until the name is valid.

This error occurs when:

  • The feature name is misspelled or contains invalid characters.
  • The feature name doesn’t match a configured feature.
  • The feature name is outdated or deprecated.

To resolve this error:

  1. Confirm the feature name is current and matches a configured feature.
  2. Check the spelling and capitalization.

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: INVALID_FEATURE_NAME
  • The feature name you used

The authentication grant type in the request isn’t valid or isn’t supported for this client. The request can’t proceed until the correct grant type is used.

This error occurs when:

  • The grant_type value is mistyped (for example, client_creds instead of client_credentials).
  • The client isn’t configured to use the requested grant type.
  • The grant type was deprecated and is no longer accepted.

To resolve this error:

  1. Verify the grant_type value matches a supported grant type.
  2. Confirm the client is configured to use the requested grant type.
  3. If the grant type you’re using is deprecated, update to a supported 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: INVALID_GRANT_TYPE
  • The grant_type value in the request

The tenant ID in your migration request isn’t valid. Agentforce can’t continue the migration until the ID is corrected.

This error occurs when:

  • The tenant ID doesn’t match the expected pattern.
  • The tenant ID contains invalid characters or is incomplete.
  • The ID came from a different system and isn’t compatible with migration.

To resolve this error:

  1. Confirm the tenant ID follows the expected format for migration.
  2. Confirm you’re using the identifier from the correct source tenant system.
  3. Remove any invalid characters from the ID.

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: INVALID_MIGRATION_TENANT_ID
  • The format of the tenant ID you used, without the actual ID value

The request failed validation because one or more parameters are missing, malformed, or out of range. Correct the parameters and try again.

This error occurs when:

  • A required parameter was omitted.
  • A parameter value doesn’t match the expected type or format.
  • A parameter is outside its permitted range or set of allowed values.

To resolve this error:

  1. Review the API documentation for the endpoint to confirm parameter requirements.
  2. Validate parameter values before sending the request.
  3. Re-send the request with corrected parameter values.

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: INVALID_PARAMETER
  • The parameter name and value that caused the failure, if shown in the error detail

The identity supplied with the request didn’t pass validation. It may be missing required attributes or be in an incompatible format for this operation.

This error occurs when:

  • A required identity attribute is missing.
  • The identity identifier doesn’t match the expected format.
  • The identity is incompatible with the operation being requested.

To resolve this error:

  1. Verify all required identity attributes are populated.
  2. Confirm the identity identifier matches the expected format.
  3. Re-resolve the identity from the source of truth 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: INVALID_PRINCIPAL
  • A description of what you were trying to do when the error occurred

The credential or token doesn’t include permission to access the requested resource. The request was rejected because the required scope isn’t granted.

This error occurs when:

  • The token was issued without the scope needed for the resource.
  • The caller’s role no longer grants the required scope.
  • The resource was moved into a more restricted scope.

To resolve this error:

  1. Re-issue the token with the required scope grant.
  2. Confirm the caller’s role still grants access to the resource.
  3. If access should be permitted, ask your Salesforce admin to update the scope.

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: INVALID_RESOURCE_SCOPE_ACCESS
  • The resource or scope the request was targeting

The platform couldn’t establish a trusted identity for this request. The internal service context is invalid or incomplete. This is a platform configuration issue, not a problem with your request.

This error occurs when:

  • An internal service identity is missing required fields.
  • The service identity isn’t configured for internal platform communication.
  • The service context didn’t originate from a trusted source.

To resolve this error:

  1. Check trust.salesforce.com for known incidents.
  2. If this error started after a recent configuration change, 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: INVALID_SERVICE_CONTEXT
  • A description of what you were trying to do when the error occurred

The service identity doesn’t have permission to access the requested resource. The request was rejected because the identity isn’t registered for access.

This error occurs when:

  • The service identity isn’t registered for access to the resource.
  • The identity in the credential doesn’t match what the resource expects.
  • The resource’s allowed identities don’t include the calling service.

To resolve this error:

  1. Confirm the service identity is registered for access to the requested resource.
  2. Verify the credential’s identity value matches what this request expects.
  3. If access should be permitted, ask your Salesforce admin to grant 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: INVALID_SERVICE_OU
  • A description of what you were trying to do when the error occurred

The Salesforce core org identifier provided is invalid or incorrectly formatted. The authentication service can’t process the request until a valid identifier is used.

This error occurs when:

  • The identifier format doesn’t match the expected UUID format.
  • The identifier contains invalid characters, typos, or extra whitespace.
  • You’re using a different type of identifier instead of the Salesforce core org identifier.

To resolve this error:

  1. Verify the identifier follows standard UUID format (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
  2. Check for typos, extra characters, or leading and trailing spaces.
  3. Confirm you’re using the correct type of identifier. Use the Salesforce core org identifier, not a different ID 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: INVALID_SF0_CORE_GUID
  • A description of what you were trying to do when the error occurred

The credential key for your org is invalid or expired. The authentication service can’t complete the request until a valid key is in place.

This error occurs when:

  • The credential key has expired and needs to be rotated.
  • The key value was truncated or copied incorrectly.
  • The key was issued for a different org or environment.

To resolve this error:

  1. Rotate or refresh the credential key for your org.
  2. Confirm the key value matches the issuer’s record exactly.
  3. Verify the key was issued for 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: INVALID_TENANT_KEY
  • A description of what you were trying to do when the error occurred

Your org is in a state that doesn’t allow this operation. It may still be provisioning, suspended, or deactivated.

This error occurs when:

  • The org is still being provisioned and isn’t yet active.
  • The org has been suspended or deactivated.
  • The org is in a recovery or migration window.

To resolve this error:

  1. Wait until the org reaches an active state and try again.
  2. If the org should be active but isn’t, contact your Salesforce admin.
  3. If the org is deactivated, the operation can’t be completed without reactivation.

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

Agentforce doesn’t recognize the time unit in your request. The request can’t be processed until the unit is valid.

This error occurs when:

  • The time unit is misspelled or isn’t supported.
  • The time unit is in the wrong format, such as singular instead of plural.
  • The time unit is empty.

To resolve this error:

  1. Use a supported time unit, such as SECONDS, MINUTES, HOURS, or DAYS.
  2. Check the spelling and capitalization.

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: INVALID_TIME_UNIT
  • The time unit value you used

The token expiry value in the request is invalid. The authentication service can’t issue a token until a valid expiry is provided.

This error occurs when:

  • The expiry time is in the past.
  • The expiry time exceeds the maximum allowed token lifetime.
  • The expiry time is below the minimum allowed token lifetime.
  • The expiry value is missing or incorrectly formatted.

To resolve this error:

  1. Confirm the expiry time is in the future.
  2. Verify the expiry value is within the allowed range. Check the API documentation for minimum and maximum token lifetime constraints.
  3. Confirm the expiry value is in the expected format.

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

The platform couldn’t complete a key rotation operation because a dependency is temporarily unavailable. Existing keys remain valid. This is usually a temporary issue. Try again later.

This error occurs when:

  • A platform dependency required for key rotation is temporarily unavailable or undergoing maintenance.
  • A temporary network issue is preventing the operation from completing.
  • The dependency is reducing capacity under high load.

To resolve this error:

  1. Wait at least 30 seconds and try again. This is a temporary error that usually clears on its own.
  2. If the error persists after several retries, check trust.salesforce.com for known incidents.
  3. Existing keys should remain functional even if rotation fails.

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

Your request is missing the application header that identifies your application to the authentication service. The request can’t be processed without it.

This error occurs when:

  • The application header isn’t included in the request.
  • The header name is incorrect or misspelled.
  • Your client isn’t configured to send the header.
  • A proxy or middleware removed the header.

To resolve this error:

  1. Add the required application header to your request.
  2. Confirm the header name is spelled exactly as required.
  3. Configure your client to include the header in every request.
  4. If you use a proxy or gateway, confirm it isn’t removing the header.

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: MISSING_APPLICATION_HEADER
  • The headers your request sends, with sensitive values removed

One or more required context headers are missing from the request. The authentication service can’t process the request without them.

This error occurs when:

  • The request didn’t include all required context headers.
  • A proxy or gateway stripped headers in transit.

To resolve this error:

  1. Confirm all required context headers are included in the request.
  2. Check any intermediaries (such as load balancers or proxies) for header stripping.

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

Your tenant deletion request is missing parameters that identify which tenant data to delete. Agentforce can’t delete anything until they’re provided.

This error occurs when:

  • A required deletion parameter isn’t included.
  • A parameter name is incorrect or misspelled.
  • A parameter value is empty.

To resolve this error:

  1. Include all required deletion parameters.
  2. Confirm each parameter name is spelled exactly as required.
  3. Provide a value for every parameter.

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: MISSING_DELETION_PARAMETER
  • The parameters your request includes, without sensitive data

The deletion request is missing a required pattern parameter. The authentication service can’t process the request without it.

This error occurs when:

  • The deletion pattern parameter was omitted from the request.
  • The pattern parameter is empty or null.
  • The parameter name is misspelled.

To resolve this error:

  1. Include a valid deletion pattern in the request.
  2. Verify you’re using the correct parameter name.
  3. Confirm the pattern value is not empty or null.

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

Your request is missing a header that the authentication service requires. The request can’t be processed without it.

This error occurs when:

  • The x-sfdc-app-context header isn’t included in the request.
  • Your client isn’t configured to send the required headers.
  • A proxy or middleware removed the header.

To resolve this error:

  1. Add the missing header to your request.
  2. Confirm your client sends all required headers for the endpoint you’re calling.
  3. If you use a proxy or gateway, confirm it isn’t removing required headers.

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: MISSING_REQUIRED_HEADER
  • The endpoint you were calling

Your request is missing a tenant identifier. Agentforce needs either a tenant ID or a core tenant GUID to process the authentication request.

This error occurs when:

  • Neither a tenant ID nor a core tenant GUID is included.
  • The identifier’s parameter name is incorrect.
  • The identifier value is empty.
  • Your client isn’t configured to send tenant information.

To resolve this error:

  1. Add either a tenant ID or a core tenant GUID to your request.
  2. Confirm the parameter name is spelled exactly as required.
  3. Confirm the identifier has 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: MISSING_TENANT_IDENTIFIER
  • The parameters your request includes, without sensitive data

The token minting request is missing a required credential. The authentication service can’t issue a new token without one to validate.

This error occurs when:

  • The request doesn’t include the authentication credential required for validation.
  • The credential parameter is empty or null.
  • The credential wasn’t included in the expected location (header, query parameter, or request body).

To resolve this error:

  1. Include a valid credential in your token minting request.
  2. Verify you’re using the correct parameter name and placement.
  3. Confirm the credential value is not empty or null.

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

The platform’s orchestration layer is temporarily unavailable. The authentication service can’t complete multi-step authentication workflows until it recovers. This is usually a temporary issue. Wait a moment and try again.

This error occurs when:

  • The orchestration layer is experiencing an outage or degraded performance.
  • A temporary network issue is preventing the authentication service from reaching it.
  • The orchestration layer is undergoing maintenance.

To resolve this error:

  1. Wait at least 30 seconds and try again. This is a temporary error that usually clears on its own.
  2. If the error persists after several retries, 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: ORCHESTRATION_SERVICE_UNAVAILABLE
  • A description of what you were trying to do when the error occurred

The identity referenced in the request doesn’t exist in the authentication service. It may have been deleted, or the identifier may be incorrect.

This error occurs when:

  • The identity identifier is mistyped or refers to a deleted record.
  • The identity exists in a different org or environment.
  • A directory sync delay is preventing the identity from being visible.

To resolve this error:

  1. Verify the identity identifier is correct and resolves to an active record.
  2. Confirm you’re using the correct org and environment.
  3. Wait briefly and try again if a directory sync delay is suspected.

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

The production org ID isn’t available for this sandbox org. The authentication service can’t complete the request until the sandbox is correctly linked to a production org.

This error occurs when:

  • The sandbox hasn’t been linked to a production org.
  • The sandbox was created without being associated with a production org.
  • The production org ID mapping is missing or wasn’t set up correctly.

To resolve this error:

  1. Confirm the sandbox is properly linked to a production org.
  2. If the sandbox should be linked to a production org, contact your Salesforce admin to verify the 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: PROD_ORG_ID_NOT_AVAILABLE
  • A description of what you were trying to do when the error occurred

The authentication service couldn’t find the public key for this identity. The key may not have been provisioned, or it may have been replaced during key rotation.

This error occurs when:

  • The key identifier is incorrect or refers to a key that was deleted.
  • Keys haven’t been generated yet for this identity.
  • A recent key rotation replaced the key and the identifier is now stale.
  • You’re working in the wrong org or environment.

To resolve this error:

  1. Verify the key identifier is correct.
  2. Confirm keys have been generated for this identity.
  3. If keys were recently rotated, ensure you’re using the current key identifier.
  4. Confirm you’re working in 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: PUBLIC_KEY_NOT_FOUND
  • A description of what you were trying to do when the error occurred

You’ve sent too many requests in a short period. The authentication service rejected the request to protect service availability. Wait before trying again.

This error occurs when:

  • You’re making too many requests in a short time period.
  • Multiple clients or processes are using the same credentials simultaneously.
  • Bursts of traffic are exceeding the allowed threshold.

To resolve this error:

  1. Wait at least 30 seconds before retrying.
  2. Reduce the frequency of requests from your application.
  3. If multiple clients share the same credentials, consolidate or stagger their requests.

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: RATE_LIMIT_EXCEEDED
  • A description of your use case and expected request volume

Your identity was confirmed, but you don’t have permission to perform this operation. The request was rejected because the required role or scope isn’t granted.

This error occurs when:

  • The caller’s role doesn’t grant permission for the operation.
  • The credential is missing a required scope or claim.
  • The targeted resource is restricted to a different set of callers.

To resolve this error:

  1. Verify the caller has the role or scope required for the operation.
  2. Re-issue the credential with the required permissions.
  3. Contact your Salesforce admin if you believe access should be granted.

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

The request failed validation. One or more fields are missing, incorrectly formatted, or out of range. Correct the request and try again.

This error occurs when:

  • A required field is missing from the request.
  • A field value doesn’t match the expected type or format.
  • A field value exceeds maximum length or contains invalid characters.

To resolve this error:

  1. Review the error response for details about which fields failed validation.
  2. Confirm all required fields are included and values match the expected format.
  3. Re-send the request with corrected values.

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

Agentforce couldn’t find the requested resource. It may have expired, been removed, or the identifier may be incorrect.

This error occurs when:

  • The identifier in the request is incorrect.
  • The resource expired or was removed.

To resolve this error:

  1. Verify the identifier is correct.
  2. Create the resource again if it expired or was removed.

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

The authentication service couldn’t complete a role operation because a platform dependency is temporarily unavailable. This is usually a temporary issue. Wait a moment and try again.

This error occurs when:

  • A platform dependency is temporarily unavailable or undergoing maintenance.
  • A temporary network issue is preventing the operation from completing.

To resolve this error:

  1. Wait at least 30 seconds and try again. This is a temporary error that usually clears on its own.
  2. If the error persists after several retries, 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: ROLE_OPERATION_FAILED
  • A description of what you were trying to do when the error occurred

Service-level authentication failed. The platform couldn’t verify the calling service’s credential. The credential needs to be refreshed or re-issued before the request can succeed.

This error occurs when:

  • The service credential has expired or been revoked.
  • The credential was issued for a different service identity.
  • A credential rotation hasn’t been applied to all instances of the calling service.

To resolve this error:

  1. Refresh or re-issue the calling service’s credential.
  2. Confirm the credential identifies the correct service.
  3. Verify the credential rotation has been deployed to all instances of the caller.

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

An org with this identifier already exists. The authentication service rejected the request to prevent creating a duplicate.

This error occurs when:

  • A previous provisioning request succeeded but the client retried after a timeout.
  • A different process already provisioned the org.
  • The org identifier is being reused for a new org.

To resolve this error:

  1. Check whether the org already exists before retrying provisioning.
  2. If a duplicate request is suspected, treat the earlier provisioning as successful.
  3. If you need a new org, use a unique 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: TENANT_ALREADY_EXISTS
  • A description of what you were trying to do when the error occurred

The authentication service couldn’t authenticate the request against your org. The credential may be expired, revoked, or issued for a different org.

This error occurs when:

  • The credential is expired, revoked, or was issued for a different org.
  • A required org-specific claim is missing or has the wrong value.
  • The credential signing key is no longer trusted by the org.

To resolve this error:

  1. Refresh or re-issue the credential for the target org.
  2. Confirm the credential’s claims match the org’s expected issuer and audience.
  3. Verify the signing key is current in the org’s trust 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: TENANT_AUTHENTICATION_FAILED
  • A description of what you were trying to do when the error occurred

The authentication service couldn’t complete org provisioning. A validation check or uniqueness rule rejected the request.

This error occurs when:

  • An org with the same identifier already exists.
  • Required org attributes are missing or fail validation.
  • The org configuration violates a business rule (for example, conflicting environment or feature settings).

To resolve this error:

  1. Confirm the org doesn’t already exist before retrying provisioning.
  2. Verify all required org attributes are supplied and valid.
  3. If validation continues to fail, contact your Salesforce admin to review configuration constraints.

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

The authentication service couldn’t complete org deletion. The org may still have active resources attached, or it may be in a state that doesn’t allow deletion.

This error occurs when:

  • The org still has active feature registrations, identities, or keys attached.
  • The org is in a state that doesn’t allow deletion (such as provisioning).
  • A downstream system rejected the delete request.

To resolve this error:

  1. Remove or deprovision any attached resources before retrying deletion.
  2. Confirm the org is in a state that allows deletion. It can’t be in provisioning or recovery.
  3. If the org appears clean but deletion is still failing, 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: TENANT_DELETE_FAILED
  • A description of what you were trying to do when the error occurred

The authentication service couldn’t find a required credential key for your org. The key may not have been provisioned, or it may have been rotated without a replacement being registered.

This error occurs when:

  • The org was provisioned without its credential keys being installed.
  • The key was rotated or deleted without a replacement being registered.
  • A key store sync delay is preventing the key from being visible.

To resolve this error:

  1. Confirm the org has its credential keys provisioned in the authentication service.
  2. Re-register the key if it was recently rotated.
  3. Wait briefly and try again if a sync delay is suspected.

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

The org identifier in the request doesn’t match a known org. It may be mistyped, not yet provisioned, or the request may have been sent to the wrong environment.

This error occurs when:

  • The org ID is mistyped or refers to an org that hasn’t been provisioned.
  • The org was deleted or isn’t yet active.
  • The request was sent to the wrong environment (for example, a sandbox org ID against a production endpoint).

To resolve this error:

  1. Verify the org identifier matches a provisioned org in the target environment.
  2. Confirm the org has been onboarded and is in an active state.
  3. If the org should exist, contact your Salesforce admin to verify provisioning.

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

Your org exists but hasn’t finished provisioning. The operation can’t complete until provisioning is done.

This error occurs when:

  • Provisioning is still in progress and not all setup steps have completed.
  • A provisioning step failed and wasn’t retried.
  • The org requires manual approval that hasn’t occurred yet.

To resolve this error:

  1. Wait for provisioning to complete and try again.
  2. Check the provisioning workflow status with your Salesforce admin.
  3. If provisioning has stalled, contact your Salesforce admin to re-run the failed 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: TENANT_NOT_PROVISIONED
  • A description of what you were trying to do when the error occurred

The authentication service’s request to Data 360 timed out. This is a temporary issue. Wait a moment and try again.

This error occurs when:

  • Data 360 is experiencing high load or slow response times.
  • A temporary network issue is causing latency between the authentication service and Data 360.
  • Data 360 is undergoing maintenance.

To resolve this error:

  1. Wait at least 30 seconds and try again. This is a temporary error that usually clears on its own.
  2. If the error persists after several retries, check trust.salesforce.com for known incidents.
  3. If you’re sending a high volume of requests, reduce the number of concurrent requests.

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

Data 360 is temporarily unavailable. The authentication service can’t complete the request until it recovers. This is usually a temporary issue. Wait a moment and try again.

This error occurs when:

  • Data 360 is experiencing an outage or degraded performance.
  • A temporary network issue is preventing the authentication service from reaching Data 360.
  • Data 360 is undergoing maintenance.

To resolve this error:

  1. Wait at least 30 seconds and try again. This is a temporary error that usually clears on its own.
  2. If the error persists after several retries, check trust.salesforce.com for known incidents.
  3. If you’re sending a high volume of requests, reduce the number of concurrent requests.

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

The authentication token service couldn’t generate the requested token because a platform dependency is temporarily unavailable. This is usually a temporary issue. Wait a moment and try again.

This error occurs when:

  • A platform dependency is temporarily unavailable or undergoing maintenance.
  • A temporary network issue is preventing the service from reaching the token endpoint.
  • The dependency is reducing capacity under high load.

To resolve this error:

  1. Wait at least 30 seconds and try again. This is a temporary error that usually clears on its own.
  2. If the error persists after several retries, 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: TOKEN_GENERATION_FAILED
  • A description of what you were trying to do when the error occurred

The integration token referenced in this request doesn’t exist. It may have been deleted, expired, or the identifier may be incorrect.

This error occurs when:

  • The token identifier is mistyped or refers to a token that was already deleted.
  • The token has expired and was automatically removed.
  • You’re working in the wrong org or environment.

To resolve this error:

  1. Verify the token identifier is correct.
  2. Check whether the token has already been deleted or expired.
  3. Confirm you’re working in the correct org and environment.
  4. If the token is no longer available, create 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: TOKEN_NOT_FOUND
  • 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: UNEXPECTED_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 cloud instance referenced in this request isn’t registered in the platform’s trust framework. The authentication service can’t authenticate the request until the cloud is registered.

This error occurs when:

  • The cloud instance hasn’t been registered in the system.
  • The cloud identifier is incorrect or mistyped.
  • The cloud registration process wasn’t completed.
  • The cloud was deregistered or removed from the trust framework.

To resolve this error:

  1. Verify the cloud identifier is correct.
  2. Confirm the cloud registration process has been completed.
  3. If the cloud should be registered, contact your Salesforce admin to verify the 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: UNREGISTERED_CLOUD
  • A description of what you were trying to do when the error occurred

The use case in the request isn’t supported. The authentication service can’t process this type of request.

This error occurs when:

  • The use case value in the request isn’t one the service handles.

To resolve this error:

  1. Confirm the use case is a supported 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: UNSUPPORTED_USE_CASE
  • A description of the authentication scenario you were attempting