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(291.2, 86%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMA%3C/text%3E%3C/svg%3E)
confirmed the Output has JSON in the body
Hi There,
Welcome to Microsoft Q&A Platform. Thank you for the question.
We would more details like which trigger you are using and if possible to share the workflow detail.
Regards,
Kamlesh Kumar
Please don't forget to click on 
or upvote 
button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is How
Want a reminder to come back and check responses? Here is how to subscribe to a Notification
If you are interested in joining the VM program and help shape the future of Q&A: Here is how you can be part of Q&A Volunteer Moderators
Hi there,
The output has a body but does the body have an appropriate array that matched the foreach?
You can't pass a non-array field to the foreach function.
@Mukesh Adhikari (AU) Thanks for reaching out. As per the error message your triggerOutput i.e. the trigger that you are using in your logic app workflow has the output body, but it doesn't have any value i.e. it is coming as null. If this is the expected output from your trigger output that the body has the null value, then you can handle this in your workflow.
Before your foreach action you can leverage the condition action to verify if the body is not null. If it is not null, then under if true you can specify the foreach statement and rest of your workflow.
Hi all,
the trigger body definitely has a JSON array in it
@Mukesh Adhikari (AU) I can see the header property and not the body of the Output trigger response. Can you please verify the body section and share the same.
I see what you mean, only header attribute is present in that Outputs. But the Service Bus message body definitely has big JSON array in it, why is it picking up only header in the logic app?
Appreciate your time.
@Mukesh Adhikari (AU) Can you confirm the content size of your message so I can reproduce the issue at my end. It looks like you may be under premium service bus and sending more than 1 MB of message content.
@MayankBargali-MSFT where can I find the content size of the message? I checked in the Message Properties for the Service Bus message, cannot find.
Also my previous comment, any obvious reason why the Logic app is only picking up the Header from the Service Bus message and not including the Body?
@Mukesh Adhikari (AU) Can you please refer to my private comment so I can review your setup and for faster resolution. To get the message size you need to peek the message so you can use the service bus explorer or custom code to view the message and the message size.