Bridge action fails in interaction flow


Note: This article applies to the web services data dip connector.

A bridge action takes the failure path in the call flow in Architect. A bridge action can fail the failure path for several reasons.

  • Search result issues
    • The connector action finds no search results or more than one search result.

      For each connector action, the connector retrieves one search result from your web services server. If a connector action finds that there are no search results or more than one search result, the failure path from the Call Bridge Action in Architect is followed. The connector returns no information from your web services server. 

      • Confirm that your input variables in Architect are compatible with and expected by your web services implementation. Architect passes the input variables, including any quotes, punctuation, and symbols, directly to your web service.
      • Search your web services server for the same data that the connector searched for.
        • If your web services server returns no results, then the failure path was correctly followed in your call flow.
        • If your web services server returns more than one result, then the failure path was correctly followed in your call flow.
        • If your web services server returns only one result, but the failure path was followed, check the connector log files to determine why the failure path was followed and no results were returned. The logs trace out if no results or multiple results are returned. 
  • Connection issues
    • The connector is unable to connect to your web services server. 

      This issue is typically due to a missing endpoint address configuration. However, this issue can also be due to security settings blocking network traffic or to an outage of the web services server.

  • Response issues 
    • The connection times out.

      The connector does not receive a response from the server before 15 seconds have passed.

      Note: Any process that is waiting for a web service is counted toward the maximum allowed concurrent processes. The connection times out after 15 seconds, regardless of a timeout setting that exceeds this amount in Architect or on the Action Details page.
    • The endpoint sends an incorrectly formatted response.

      The connector cannot convert the response body into the correct format.

      • Check the log files for information about why the connector was unable to complete the request.
      • Contact your web services provider. 
    • The endpoint attempts to call a non-implemented method.

      This issue occurs when you do not implement one of the default connection actions but your web service still attempts to call it.

      • Check the log files for information about why the connector was unable to complete the request.
      • Contact your web services provider. 

For more information about the connector, see About the web services data dip connector.