Trigger Actions with Buffer Size Fields
Some Trading Partner Trigger actions have a Reading Buffer Size field, and/or a writing Buffer Size field. If present, they are located on the Advanced tab in the trigger action. Below is the definition of each field.
-
Reading Buffer Size - This is the amount of data (KB) that can be read in 1 request.
-
Writing Buffer Size - This is the amount of data (KB) that can be written in 1 request. When the write buffer is full, the system pushes the data to its destination.
As a general rule, the data transfer speed increases as the buffer sizes increase. SFTP can be sensitive to buffer size. Typically 32 KB for both the read and write buffers work the majority of the time. If an SFTP trading partner generates a protocol error due to a buffer limitation, you may need to modify these fields accordingly.
The grid below depicts the name of the Trading Partner actions that were updated with the new field(s), and their default buffer sizes. Some were updated to include both the Reading and Writing Buffer Size fields, and some were updated to include only the Writing Buffer Size field.
| Trading Partner Action | Reading Buffer Size Default Value (KB) | Reading Buffer Size Minimum Value (KB) | Reading Buffer Size Maximum Value (KB) | Writing Buffer Size Default Value (KB) | Writing Buffer Size Minimum Value (KB) | Writing Buffer Size Maximum Value (KB) |
|---|---|---|---|---|---|---|
| Trading Partner File Download | 32 | 1 | 512 | 512 | 1 | 1024 |
| Trading Partner File Upload | N/A | N/A | N/A | 32 | 1 | 512 |
| Trading Partner Regex File Upload | N/A | N/A | N/A | 32 | 1 | 512 |
| Trading Partner Regex File Download | 4 | 1 | 512 | 512 | 1 | 1024 |
| Trading Partner Copy File | 4 | 1 | 512 | 512 | 1 | 1024 |
| Trading Partner Copy Regex File | 4 | 1 | 512 | 512 | 1 | 1024 |
| Trading Partner Move File | 4 | 1 | 512 | 512 | 1 | 1024 |