In my previous post I showed you how to create a flat file decoding Logic App. When I first tested this I used URL generated when I first saved the Logic App to create a post command using the compose feature of fiddler.
![image image](http://blogs.recneps.org/image.axd?picture=image_thumb_14.png)
The body of the message contained a single cvs row that I wanted to debug and I was hoping to see the response containing the xml representation of the csv file.
When I submitted the request, fiddler displayed an 502 error – Bad Gateway
![image image](http://blogs.recneps.org/image.axd?picture=image_thumb_15.png)
This wasn’t very helpful and I needed to understand what had gone wrong.
Navigating to the Logic App in the Azure Portal I noticed that the Overview blade showed the runs for the Logic App
![image image](http://blogs.recneps.org/image.axd?picture=image_thumb_16.png)
Clicking the failed run opened a new blade in the portal which showed my Logic App and it failing at the Flat File Decoding stage
![image image](http://blogs.recneps.org/image.axd?picture=image_thumb_17.png)
Clicking the Flat File Decode caused it to expand and show me a more detailed (and useful) error
![image image](http://blogs.recneps.org/image.axd?picture=image_thumb_18.png)
The error told me that the Flat File Decode couldn’t find the CR/LF at the end of the line. As I’d put a single line of text and no CR/LF the decoding failed.
I repeated the POST, this time with the CR/LF at the end of the body and the Logic App worked correctly and the correct xml representation of the csv was displayed in the body of the response.