Data action fails during testing

Note: This article applies to the AWS Lambda, Genesys Cloud, Google, Microsoft Dynamics 365, Salesforce, web services, and Zendesk data actions integrations.

When you test data actions for the data actions integrations, the actions can fail due to authentication, certificate, processing, or remote endpoint errors. 

Authentication errors

The following content applies to all data actions integrations.

These errors occur in the remote third-party service during authentication to the remote endpoint. 

Example response

{
    "errorCode": "INVALID_CREDENTIALS",
    "status": 400,
    "correlationId": "43436e96-5c19-4c52-b951-4ea05d9a9af7",
    "entityName": "msDynamics",
    "userMessage": "There was an issue validating the credentials.",
    "userParams": [],
    "details": [
        {
            "errorCode": "ACTION.AUTHENTICATION"
        }
    ],
    "errors": [
        {
            "errorCode": "INVALID_CREDENTIALS",
            "status": 400,
            "userMessage": "Request to backend service failed.  Response from web service: {\"error\":\"invalid_grant\",\"error_description\":\"AADSTS50126: Invalid username or password\\r\\nTrace ID: 5a830f2e-1978-47f4-a49c-8bfb208f8100\\r\\nCorrelation ID: 0ac36657-3a9a-43b9-9101-fde463adba2a\\r\\nTimestamp: 2019-02-11 14:17:11Z\",\"error_codes\":[50126],\"timestamp\":\"2019-02-11 14:17:11Z\",\"trace_id\":\"5a830f2e-1978-47f4-a49c-8bfb208f8100\",\"correlation_id\":\"0ac36657-3a9a-43b9-9101-fde463adba2a\"} [53df0750-c233-4434-9d36-6377ededb014]",
            "userParams": [],
            "details": [],
            "errors": []
        }
    ]
}

For Salesforce data action integration, ensure that you enable Allow OAuth Username-Password Flows settings in OAuth and OpenID Connect Settings. For more information, see Salesforce Release Notes.

Certificate errors

The following content only applies to the web services data actions integration.

This error occurs when web services data actions reject the certificate from the remote endpoint.

Tip: To check for issues with your certificate configuration, point an HTTPS security checker like https://www.ssllabs.com/ssltest to your web service.

These errors can occur for a couple reasons.

  • The root certificate for your website is self-signed or not publicly trusted. Web services data actions require certificates to be issued by publicly trusted certificate authorities.
  • The web server does not provide an intermediate certificate in the trust chain. Web services data actions require that endpoints provide any intermediate certificates during TLS negotiations. To fix this issue, check the documentation for the web service or consult your vendor for the web service.

Example response

{
  "message": "The server encountered an unexpected condition which prevented it from fulfilling the request.",
  "code": "internal.server.error",
  "status": 500,
  "messageParams": {},
  "contextId": "5dfe55e3-b172-406d-94f7-5d826afd4c0e",
  "details": [
    {
      "errorCode": "ACTION.REMOTE_ENDPOINT"
    }
  ],
  "errors": [
    {
      "message": "REST call for action execute failed. Message:Unable to send message after 2 attempts, due to: SunCertPathBuilderException: unable to find valid certification path to requested target [5dfe55e3-b172-406d-94f7-5d826afd4c0e]",
      "code": "INTERNAL_SERVER_ERROR",
      "status": 500,
      "messageParams": {},
      "details": [],
      "errors": []
    }
  ]
}

Processing errors

The following content applies to all data actions integrations.

These errors occur during the internal processing of a data action such as executing a data action that does not exist, a body template not being valid JSON, or JSONPath errors.

Example response

{
    "errorCode": "NOT_FOUND",
    "status": 404,
    "correlationId": "a04c66e5-a2ec-46f3-9c7f-d904cd7e46cc",
    "userMessage": "Action with id static_-_Salesforce-GetAccountByPhoneNumber_-_37f5a780-70d7-408c-9cf7-8cd4cc7265fc was not found",
    "userParams": [],
    "details": [
        {
            "errorCode": "ACTION.PROCESSING"
        }
    ]
}

The error can also occur when you create a data action with non-JSON content type in the Accept header. For example, if you have text/html in the Accept header, then you get the following response:

Example response

{
    "status": 400,
    "errorCode": "INVALID_SCHEMA",
    "userMessage": "The 'Accept' header only supports json content types when specified",
    "userParams": [],
    "correlationId": "7930ce0c-ec9e-4929-9a70-0fe087b518b2",
    "details": [
        {
            "errorCode": "ACTION.PROCESSING"
        }
    ]
}

Remote endpoint errors

The following content applies to all data actions integrations.

These errors are returned from the remote endpoint. In the following example, an action attempts to retrieve a contact based on a phone number, but the contact doesn’t exist in the service that the action is contacting. 

Example response

{
    "userMessage": "The requested resource was not found.",
    "errorCode": "NOT_FOUND",
    "correlationId": "fb9dda21-979f-4718-b772-8ecc3fbb7dac",
    "details.errorCode": [
        "ACTION.REMOTE_ENDPOINT"
    ],
    "status": 404
}

When an action set without a header executes and the remote endpoint returns a non-JSON response, you get the following error:

{
    "status": 400,
    "errorCode": "BAD_REQUEST",
    "userMessage": "The request could not be understood by the server due to malformed syntax.",
    "userParams": [],
    "correlationId": "fbb8bb72-0637-4028-b7d8-caba6686244b",
    "details": [
        {
            "errorCode": "ACTION.REMOTE_ENDPOINT"
        }
    ]
}

For more information, see Test data actions for integrations.

For more information about the integrations, see About the data actions integrations.