Usage Guidelines and Limits

Polling Triggers

Projects

Webhooks

Cloud Messaging

Here are the details on Message restrictions in Cloud Messaging.

Flow Services

Here are the Best Practices for using Flow services.

Node.js CLI-based Connectors

Logs and Monitoring

Spoke Tenants

Under Spoke tenants, authorizations can be created using only Custom Authorization option. Default Authorization option is disabled. Learn more about Spoke Tenants

Hybrid Integration

Message size limit

The maximum size limit of an encoded service output to be transported over Hybrid Integration is 50 MB.

The following encoding limits are enforced:

• java.lang.String uses a fixed width encoding of 2 bytes per java.lang.Character. In general, all data types excluding java.lang.Integer and java.lang.Byte are converted to java.lang.String before encoding. For example, a java.lang.String must be less than 25 MB, however, a byte[] must be less than 50 MB.
• Each field or value within the Service Output is framed with metadata during encoding, and this is added to the encoded data.
• The Service Output being transported is encoded into a single cumulative piece, so consideration for the number of fields and their cumulative sizes are needed.

Connectivity

Large Payload Handling Capabilities

Sending large payloads for all the connectors in Cloud is currently not supported except for the AWS S3 connector. AWS S3 backend provides the capability to handle large documents, hence it is supported.

The payload size is limited by the available memory and is dependent on the volume of transactions that are flowing through the system at a given point of time.

WSDL Support

Cloud REST resource supports only one type of message builder and formatter for all the response codes.

Cloud does not support the RPC/encoded style WSDL and the RPC/literal style WSDL.

Salesforce Events

Salesforce events can be retrieved only if you are using Salesforce v37.0 or later. Currently, the replay options are supported only for Salesforce Push Topic.

Limitations are also imposed by Salesforce backend.

See the following Salesforce documentation for examples on the limits:

• https://developer.salesforce.com/docs/atlas.en-us.234.0.platform_events.meta/platform_events/platform_event_limits.htm
  
• https://developer.salesforce.com/docs/atlas.en-us.change_data_capture.meta/change_data_capture/cdc_allocations.htm

Connector Development Limitations

Nested business objects are not handled while creating a custom operation. Provide the details associated with business objects for complex operations when you are creating a custom operation. Currently, the CloudStreams APIs support only one-level business object fields.

Multipart Form Data

There is no limit on the size of the file part that is sent as a part of multipart. The size of the file included in the multipart request is dependent upon the available heap size of the server.

Streaming Listener Limitations

Before using streaming capabilities, it is important to understand the underlying limitation of the protocol and the SaaS backend, for example, Salesforce.

If there are network, proxy, or firewall connectivity related issues or delays, you may not receive the messages. In such cases, investigate the network and connectivity.

Note: The protocols that provide the streaming listener capability are public protocols which run over HTTP like Bayeux.
These protocols are not guaranteed protocols. They do not ensure delivery of the messages in a guaranteed way.

Streaming Providers Limitations

Due to network, proxy, or firewall connectivity related issues, the default timeout values for Connection Timeout (ms) may not be enough in your environment. Check the timeout settings based on your network conditions and set the values for Connection Timeout (ms).

Due to latency and other issues, some networks may take a long time to exchange messages. In such cases you may see timeout errors. To avoid that, increase the timeout values and see what values fit your organization. This is applicable for all the outbound and inbound timeout configurations.