Azure-docs: Does this apply to triggers?

[JasonBSteele]

There is no mention on whether this applies to Triggers as well. Looking at the settings for HTTP Request it doesn't look it does, but why would this be different from an HTTP Get?

Knowing one way or the other would be useful - and if not available, why.

---

Document details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 4dfc3213-ed4c-aa45-c276-94cdc27bf773
• Version Independent ID: 8c4aa841-6e3b-ee0b-970f-1a8a70335f6f
• Content: Handle large messages - Azure Logic Apps
• Content Source: articles/logic-apps/logic-apps-handle-large-messages.md
• Service: logic-apps
• GitHub Login: @shae-hurst
• Microsoft Alias: shhurst

[Grace-MacJones-MSFT]

Hi @JasonBSteele, Thanks for the feedback! We are currently investigating and will update you shortly.

[PramodValavala-MSFT]

@JasonBSteele
The HTTP Request trigger does not support chunking and also has a few other limits that you can refer to here.

That being said, the HTTP Request trigger is best used to start asynchronous jobs or as webhooks. If your use case requires dealing with large payloads (like file uploads for example), its best to upload such files to a blob container and then use the Blob trigger instead.

[PramodValavala-MSFT]

@JasonBSteele Just following up... Hope my comment answers your query

[JasonBSteele]

Hi @PramodValavala-MSFT , thanks for getting back to me.

Thanks for the tip about using a blob and triggering from that instead - this is something we are considering. However it is a bit clunky to have to go through a blob - and we can't even use a Logic App to receive the message and create the blob! We'll have use a Function or write directly via the REST API.

My OP is more about the fact that this isn't mentioned anywhere and no rationale is given. It seems illogical that I can use chunking with an HTTP Action but not with the Trigger.

[shae-hurst]

Hi @JasonBSteele,

Triggers, by current design cannot "wait" around for all of the data to be received via separate chunks which are contained in different HTTP messages. Triggers don't have access to state in the way that actions do, and they are scheduled behind the scenes very differently.

What @PramodValavala-MSFT suggested about the trigger on blob update is a great way to handle this.

[JasonBSteele]

@shae-hurst, thanks you for the explanation - that does make it much clearer. It would be great if this could be added to the documentation to make it clear that Triggers don't support this feature and why.

[shae-hurst]

Yes I will add a short comment about this to the doc. Thanks for the feedback!

[PramodValavala-MSFT]

@shae-hurst Thanks for helping out! I am assigning this issue to you.

@JasonBSteele Thanks for contributing to MS Docs! We will be assigning this issue to the author to update accordingly.

[ecfan]

@shae-hurst Hi Shae, any news on updating this article? Last comment on this issue is 2+ weeks old. Thanks!

[shae-hurst]

I fixed it and merged it a couple weeks ago.

[shae-hurst]

@ecfan is there a task or something I need to close?

[ecfan]

@shae-hurst Thanks, we just need to close out the GitHub issue and close the loop for the customer when the issue is resolved. I'll ask CXP to close the GitHub issue now.

@PramodValavala-MSFT #please-close