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(0, 7.000000000000001%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
Hi All,
I have created a logic app, Added HTTP Request Sent Trigger and then added the Outlook Email part and DID run the trigger and received email w/o any issues.
Now i created a test pipeline and then added a web activity to test it , in the web activity in the Body part i have the following JSON
{
"Pipeline":"@{pipeline().Pipeline},
"ErrorMessage":"@{activity('Copy data1').Error.message}",
"DataFactoryName":"@{pipeline().DataFactory}",
"Runid":"@{pipeline().RunId}"
)
When I run the pipeline it is failing with the following error, i have looked up multiple documents and still i could not find a solution. Please advice.
Error Message
{"error":{"code":"InvalidRequestContent","message":"The request content is not valid and could not be deserialized: 'After parsing a value an unexpected character was encountered: E. Path 'Pipeline', line 3, position 1.'."}}
Hi @bk ,
Just checking in to see if the below answer helped. If this answers your query, do click 
and upvote 
for the same. And, if you have any further query do let us know.
@Nandan Hegde
Thanks , I hardcoded one by one and it is the ')' and not '}' i had in the body of the web. Fixed.
Thanks
Hi @bk ,
Could you please mark your answer as accepted answer? Accepted answers helps community as well.
Hey @bk ,
As you mentioned that you are receiving the mails when you are directly triggering the logic app but the issue is during ADF execution, can you please hardcode all the values initially in the body and test the execution and slowly and gradually parameterize one by one to debug the cause of that issue?
That might help us in pin pointing the source which would help us in focusing our cause analysis.