Status Codes and Error Responses

Each request returns a status code or error response to indicate whether the request was successful. Errors can have several causes.

When an error occurs or when a response is successful, the response header contains an HTTP code, and the response body usually contains:

The HTTP response code
The message accompanying the HTTP response code

HTTP response code	Description
2xx	Query successfully executed and response data returned.
400	(BAD REQUEST) The argument or query you supplied in the request isn’t valid, and we can't search based on your query. Confirm the accuracy of your query or contact Salesforce Customer Support.
403	(FORBIDDEN) We can't authenticate your request, so try to confirm your configuration or, you don't have permission to view the requested data on the connected system. Update your credentials on the connected system or contact Salesforce Customer Support for help.
404	(NOT FOUND) We can’t find something necessary to satisfy your query. Confirm the accuracy of your query or contact Salesforce Customer Support.
409	(CONFLICT) We can't search based on your query. Confirm the accuracy of your query or contact Salesforce Customer Support.
429	(TOO_MANY_REQUESTS) Looks like we're trying to process too many requests at once. Try again in a moment or contact Salesforce Customer Support.

400 (BAD_REQUEST)

Table 1. 400 (BAD_REQUEST) ILLEGAL OPERATION
Issue	Cause	Solution
Illegal Argument	At least one of the arguments provided in the query is invalid, such as an invalid field used for selection or filtering.	Check that the fields are valid and try again.
Hinted Connected Systems not queried	At least one of the connected systems with a specialized query isn't queried. For example, no mappings to the connected system that is specified in the query.	Check that your mappings query these connected systems and try again.
Invalid Query Routing	A query is present but invalid because it uses incorrect arguments in an expand.	Change or remove the invalid query and try again.
Invalid Metadata Repository Key	An unsupported metadata repository key is specified. For example, the metadata repository key isn’t URL-encoded and contains invalid characters.	Make sure your metadata repository key is in the form of:`{cloud}/{environment}/{MRK}:` (MRK = MetadataRepostioryKey) and try again.
Multiple Matching Connected Systems	More than one connected system has the same API name.	Remove and reconnect one of the duplicate connected systems so that only one connected system is mapped to a single name. Then try again.
Multiple Query IDs	Multiple problems with IDs.	Check the ID values and try again.
Repeated Query Parameter Name	Multiple query parameters have the same key or name, so it's unclear which value to use.	Remove any invalid or duplicate query parameters and try again.
Unexpected Query Parameter Name	A query parameter can’t be handled.	Remove any extraneous or invalid query parameters and try again.

Table 2. 400 (BAD_REQUEST) UNSUPPORTED_OPERATION
Issue	Cause	Solution
Unsupported Operation Exception	The query is valid but the feature isn’t yet implemented.	Remove query components relying on unsupported features.

Table 3. 400 (BAD_REQUEST) UNSUPPORTED_QUERY
Issue	Cause	Solution
Invalid DF API Version	Unsupported Data Federation API version specified in the BaseURL.	Fix the specified API version.
Invalid Dialect Query	Unsupported dialects such as OData, GraphQL, or SOQL.	Change the dialect to OData and try again.
Not Acceptable Exception	There are too few arguments for the API dispatcher to match the request to an implemented request handler.	Include all of the necessary path parameters for the query and try again.
Malformed Query	The query to DF isn’t valid, for example, when querying a child entity of a connector that doesn’t support hierarchies.	Remove query components relying on unsupported hierarchies and try again.

403 (FORBIDDEN)

Table 4. 403 (FORBIDDEN) UNAUTHORIZED
Issue	Cause	Solution
Malformed Header	Your authorization header doesn’t start with the required C2C prefix.	Make sure the authorization header is valid and try again.
Missing Header	You didn’t send an authorization header in your request.	Make sure the authorization header is valid and try again.
Unexpected Security Error	Unexpected security error.	Contact Salesforce Customer Support.

Table 5. 403 (FORBIDDEN) DATASOURCE_UNAUTHORIZED
Issue	Cause	Solution
Connector Authorization Error	A connector encounters an authorization failure while trying to communicate with the connected system.	Update credentials on the connected system and try again.

404 (NOT_FOUND)

Table 6. 404 (NOT_FOUND)
Issue	Cause	Solution
Jersey Not Found	An invalid endpoint was specified.	Fix the invalid endpoint and try again.
No Matching Connected System Connection	A Connected System Connection name was specified that didn’t correspond to a known Connected System Connection	Specify a knownConnected System Connection name and try again.
No Matching Connected System	There’s a specified connected system name that doesn’t correspond to a known connected system key.	Specify a valid connected system name.
No Matching Managed Tenant	A referenced source tenant from a transformation isn’t present.	Add the missing trust relationship for the necessary source tenant and try again.
No Matching Transformation Repository	An unsupported metadata repository key is specified in the DF API URL. The requested metadata repository isn’t found.	Specify a valid transformation repository and try again.
No Matching Transformation Repository Version	An unsupported metadata repository version is specified in the DF API URL.	Specify a valid transformation repository schema version and try again.
No Matching Transformations	There are no transformations found for the target entity.	Specify a valid transformation repository or schema, version, or target entity combination and try again.
No Matching Connected System	A referenced source tenant from a transformation is not present in the Connected System set.	Add the missing trust relationship so that the necessary source tenant is in the Connected System set and try again.
Salesforce Connect Error	Salesforce Connect does not have the requested entity definition.	Specify a target entity that is present in the schema and try again.

409 (CONFLICT)

Table 7. 409 (CONFLICT) ILLEGAL_ARGUMENT
Issue	Cause	Solution
Multiple Field Mappings	There are multiple mappings for the same target field when trying to convert the target query's filter to the source or intermediate query schema.	Remove all but one mapping that points to the target field in the faulty transformation and try again.
Missing Field Mapping	There are no mappings for the target field when trying to convert the target query's filter to the source or intermediate query schema.	Add a mapping to the target field in the faulty transformation and try again.

429 (TOO_MANY_REQUESTS)

Table 8. 429 (TOO_MANY_REQUESTS)
Issue	Cause	Solution
Rejected Execution	The Connect Center rejects the request when too many tests are added to the queue and the rate limit is reached.	Wait for some of your outstanding requests to be completed or increase your quota and try again.