Logic App flat file transformation - xml transform fail with large file

Category: azure logic apps


MaxLisi on Wed, 12 Apr 2017 16:07:01

Hi all,

I designed a flow with following steps:

  • Pick up a file from One Drive when created
  • Flat File Decoder to transform the content inXML
  • XML Transform to map the incoming XML to another XML (another xml flat file schema)
  • Flat File Encoder
  • File creation in One Drive

Everithing works fine, but if I put in input a file that is 3.8MB size, the File Creation step in One Drive fails with the following error: "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."

The XML Transoform step was succeeded, but removing it, so taking the "Create file" file content from the output of the Flat File Decoder step, everything works fine and the file is created in One Drive (size 14MB...).

So I suspect that XML Transform step does not generate output with large file, even if was succeeded.

Does anyone faced to the same situation?




sujith reddy komma on Wed, 12 Apr 2017 17:54:48

Hi maxLisi,

I have Checked the File Size of the Logic Apps in the below Article. It Looks the max File Size is 100 MB.


But it did mention that some Connectors may not support 100 MB.

For Integration Accounts, Schmea Size and XSLT Sizes looks like below

Schema 8MB

XSLT      2MB

How Ever, These are the Sizes of XSD and XSLT.

There is no Reference on Transfrom XSLT Connector.

This Might not be the Exact answer for this,Just Sharing may be others can Help you.



Padma Chilakapati on Thu, 13 Apr 2017 22:10:36

@MaxLisi:  Can you share the failed run ids? Also check your transform outputs, you are processing the supported message size in transform and it should transform the message.

You can also share your input file, schema and XSLT to padmavc@microsoft to verify/repro the issue.

@Sujith, these limits are for uploading schema and XSLT in integration account, not for message processing.


B_Varun on Mon, 11 Jun 2018 09:03:02


I am having the same issue, did you get any resolution?