This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(121.6, 93%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJK%3C/text%3E%3C/svg%3E)
Hello,
I am continuing to get this error when I try to debug this pipeline. ![111054-screen-shot-2021-07-01-at-123900-pm.png][1]
This is the dataset that the error is referring to. ![110998-screen-shot-2021-07-01-at-15152-pm.png][2]
An Azure service for ingesting, preparing, and transforming data at scale.
So I have tried to resolve the problem by applying a different value for the executing pipeline activity. This has given me some success but
now I am having connection issues with the http server. 
This is the error. I feel like the solution is really simple.
Answer accepted by question author
For those who are seeing similar issues, I have resolved the problem. Keep in mind that csv filed formats DO NOT save the new data format that you input.
My specific incident required a yyyy-mm-dd date format as my input. Date formats are tricky for csv files so alter your data pipeline parameters then
you should be in good shape.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 9%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
Hi @John Kim ,
Glad to know that your issue was resolved and appreciate much for sharing your findings here with community as it would be beneficial for others reading it. :)
Have a good day!
Hi @John Kim ,
Welcome to Microsoft Q&A forum and thanks for reaching out.
By looking at the error message it seems like the error is from the http server end. I would also request you to double check if it is an intermittent issue. If so then you can try setting up retry option which would avoid this issue.
In case if the issue is consistent, then you will have check the input values for the HTTP call for the failed pipeline run and do same testing using same input data in Postman to verify if the issue is related to any of the input data for the HTTP call. And also please make sure the returned data is in expected format. You can also verify the failed HTTP response with the success response by doing a comparision.
Hope this info helps. Do let us know how it goes.
----------
Please don’t forget to Accept Answer and Up-Vote wherever the information provided helps you, this can be beneficial to other community members.
Hi @John Kim ,
Following up to see if the above suggestion was helpful to resolve your issue or are the issue persists? In case if you have already found a solution, please do consider to share it here with community, as it would be helpful for others reading this thread.
Thank you.
Hi @John Kim ,
We still have not heard back from you. Just wanted to check if the above suggestion was helpful? If it answers your query, please do click “Accept Answer” and/or Up-Vote, as it might be beneficial to other community members reading this thread. And, if you have any further query do let us know.