Limitations¶
It is recommended that you read the following before you create any integration flows. The limitations listed here are applicable to each OU.
Item |
Cloud/Remote Flow |
Limitations |
---|---|---|
Max number of computing resource that can be applied for |
Cloud Flow |
100 CU |
Max number of flows that can be created |
Cloud & Remote Flows |
100 |
Max number of input nodes for a single flow |
Cloud & Remote Flows |
1 |
Max number of nodes for a single flow |
Cloud & Remote Flows |
50 |
Max number of flows that can be published |
Cloud Flow |
Depends on the available computing resource |
Max number of running instances for a single flow |
Cloud Flow |
10 |
Max computing resource for a single instance |
Cloud Flow |
8 CU (4 Core CPU + 16 GB Memory) |
Max number of flows that can be selected at one time in the Dashboard page |
Cloud Flow |
5 |
Max number of rules that can be added when configuring flow alerts |
Cloud Flow |
3 |
CPU usage percentage threshold range when configuring flow alerts |
Cloud Flow |
From 30% to 100% |
Memory usage percentage threshold range when configuring flow alerts |
Cloud Flow |
From 50% to 100% |
Flow execution error threshold range when configuring flow alerts |
Cloud Flow |
From 1 to 24 hours, from 1 to 999 times |
Max amount of cached data for MQTT server in Server Configurations |
Cloud Flow |
1GB |
Max period of cached data for MQTT server in Server Configurations |
Cloud Flow |
10 minutes |
Max number of MQTT server connections |
Cloud Flow |
1,000 |
Max period of log storage for flows |
Cloud Flow |
15 days |
Max period of log storage for nodes |
Cloud Flow |
7 days |
Max storage for the input/output msg of each node log |
Cloud Flow |
8KB |
Max space of downloaded file storage |
Cloud & Remote Flow |
12GB |
Max period of downloaded file storage |
Cloud & Remote Flow |
30 days |