CloudStreams Server fails to parse XML payloads around 3 MB with the following error message: Exception parsing native service provider com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in attribute value. 

The 'Get_Workers' Workday operation under the 'Human Resources' functional area is one such connector service that will fail when a page of workers is fetched. 

Workaround: Disable SOAP validation by setting 'enableSoapValidation' as false in <SAG-Installation-Dir>\IntegrationServer\instances\default\config\wss\axis2.xml and then restart Integration Server.

The lookup details provided in the REST connector descriptor for any resource are not added to node-hints of a Cloud Connector Service.

The resource metadata is not passed in the implementation where node-hints are created for a Cloud Connector Service.

There is currently no workaround for this issue.

While retrieving the custom operation data for a SOAP connector, the header values are not completely populated. This issue does not impact any other API usage for the service.

Workaround: View the header values in the Designer.

While retrieving the custom operation data for a Salesforce SOAP connector, the debugging header value is not populated. This issue does not impact any other API usage for the service.

Workaround: View the debugging header value in the Designer for the same service.

When multiple values are passed as a comma-separated list in a header, the values are sent, however, the input added in the Cloud Connector Service gets directly mapped to the output, leading to incorrect output.

Workaround: Use a single value in the header.

In the Microsoft Azure Storage connector, for the putBlob operation,* configuring the blob name with the special character slash ('/') is not allowed.

In the Microsoft Azure Storage connector, for the putBlob operation, configuring the blob name with consecutive slashes (e.g. "ab//cc") or beginning with a slash (e.g. "/testfile") results in a 403 error.

Workaround: There is currently no workaround for this issue.

Even though the connection is already enabled, enabling a listener triggers an unnecessary login call to Salesforce.

This issue is observed for basic connections only.

There is currently no workaround for this issue.

Nested business objects are not handled while creating a custom operation.

While creating a custom operation, details associated with business objects can be provided for Complex type operations.

Currently, the CloudStreams APIs support one-level business object fields only.

Workaround: The custom operation that is created using the API can be updated in the Designer. Choose the related or nested business objects while updating the custom operation.