When upload file more that 200MB to a blog, the blog trigger a Logic App Workflow not get activate

Question

When upload file more that 200MB to a blog, the blog trigger a Logic App Workflow not get activate

Anonymous

we create a blog storage that when a file is drop on that its activate a Logic App workflow trigger that process that file. For file around more that 200MB this trigger don't get activate less it work fine.

We need process files almost to 17GB size.

1 answer

Your answer

Answer 1

MayankBargali-MSFT 70,941 Moderator

@Anonymous Azure blob connector supports a maximum 1 GB file size with chunking enabled as mentioned in the General Limit section. For files greater than 50 MB and less than 1GB you need to follow mentioned here.

Blob Storage triggers don't support chunking. When requesting file content, triggers select only files that are 50 MB or smaller. To get files larger than 50 MB, follow this pattern:

Use a Blob Storage trigger that returns file properties, such as When a blob is added or modified (properties only).
Follow the trigger with the Blob Storage Get blob content action, which reads the complete file and implicitly uses chunking.

As there is a limitation of 1GB file you can offload the processing of file functionality to azure function by calling the function from the logic app. To handle large messages within logic app you can refer here but please refer to the limit of individual connectors.

Anonymous

2022-01-20T15:05:09.013+00:00

Thanks a lot.
we really want to upload files to the blob of around 17GB, after uploading it to fire the trigger and then process that file using an azure function.

I found that in the host.json of the azure function I can put those maximums in the properties like Runtime.FlowRunActionJob.MaximumActionResultSize
what the documentation that I have read does not say what would be the maximum that I can put in those properties and if they would reach 17GB.
please any recommendation.
MayankBargali-MSFT 70,941 Reputation points Moderator

2022-01-25T09:59:14.857+00:00

@Anonymous I believe you are talking about logic app standard Runtime.FlowRunActionJob.MaximumActionResultSize where you can specify the maximum size in bytes that the combined inputs and outputs can have in an action but your connector limit should be still there. You can either use the azure function storage trigger/event grid trigger to process larger files from your function app.
If you still want to use the logic app then you need to pass the storage URL from the logic app to your azure function and do the processing of your file.

Share via

When upload file more that 200MB to a blog, the blog trigger a Logic App Workflow not get activate

1 answer

Your answer