Azure Logic Apps: are you handling large blobs? Keep memory usage under control.
Handling large blob files in Azure Logic Apps for Dynamics 365 Business Central integration can cause excessive memory usage because built-in connectors load all data into memory. To prevent out-of-memory exceptions, monitor workflow concurrency, ensure 64-bit platform settings, and delegate large file processing to Azure Functions or inline code.
post Stefano Demiliani
"The built-in connectors load all the informations into memory by design."
Key points
- Built-in Azure Logic Apps connectors load entire files into memory, causing high memory consumption with large blobs
- Logic Apps Standard in WS1 plan (3.5 GB total) can run out of memory when processing multiple large files or concurrent executions
- Solutions include monitoring workflow concurrency, verifying 64-bit platform configuration, and delegating file processing to Azure Functions
- Using Azure Functions or inline code functions significantly improves performance and memory efficiency for large file handling
Quotes
- “The built-in connectors load all the informations into memory by design.” (Explains the root cause of memory issues when processing large blobs in Logic Apps workflows)
- “Usually the built-in version of a connector provides better performance than the managed counterpart, so it’s why they are proposed as default.” (Shows the trade-off between performance and memory usage when choosing connector types)
Context
- Features: Blob Storage connector, built-in connectors, managed connectors, Azure Functions integration, workflow concurrency monitoring, inline code functions
Source: Stefano Demiliani, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.