Use an SFTP-SSH trigger that returns only file properties. To get files larger than 15 MB, follow this pattern instead: When requesting file content, triggers select only files that are 15 MB or smaller. SFTP-SSH triggers don't support message chunking. This table shows which SFTP-SSH actions support chunking: Action In this case, the chunk size for actions that don't support chunking ranges from 5 MB to 50 MB. This attribute means you can use the same connection for both actions that support chunking and actions that don't support chunking. In different scenario, if your logic app is timing out, for example, when using 15-MB chunks, you can try reducing the size to 5 MB.Ĭhunk size is associated with a connection. To reduce the number of calls, you can try setting a 50-MB chunk size. Adaptive chunking results in several calls, rather that one call. For example, suppose you have a 45-MB file and a network that can that support that file size without latency. You can override this adaptive behavior when you specify a constant chunk size to use instead. This connector's ISE-labeled version requires chunking to use the ISE message limits instead. Dynamic sizing is based on factors such as network latency, server response time, and so on.įor logic apps in an integration service environment (ISE), However, this size can dynamically change, starting from 5 MB and gradually increasing to the 50-MB maximum. SFTP-SSH actions that support chunking can handle files up to 1 GB, while SFTP-SSH actions that don't support chunking can handle files up to 50 MB.
The SFTP-SSH connector currently doesn't support these SFTP servers: If you're new to logic apps, review What is Azure Logic Apps?įor differences between the SFTP-SSH connector and the SFTP connector, review the Compare SFTP-SSH versus SFTP section later in this topic. For example, if you regularly retrieve files from your SFTP server, you can send email alerts about those files and their content using the Office 365 Outlook connector or connector. You can also include other actions that use the output from SFTP-SSH actions. You can then use actions to perform various tasks on your SFTP server. In your workflow, you can use a trigger that monitors events on your SFTP server and makes output available to other actions.