![](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(185.6, 66%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAA%3C/text%3E%3C/svg%3E)
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,217 questions
![](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(12.8, 1%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESF%3C/text%3E%3C/svg%3E)
Capturing the input JSON for failed API calls in a Logic App can be challenging since it's not always logged by default. However, you can try using the AzureDiagnostic table in Log Analytics, which holds detailed information about each Logic App run, including inputs—if logging was set up properly.
If you don't find the input JSON there, it might be because input logging wasn't enabled in the Logic App's diagnostic settings at the time of those calls. To avoid this issue in the future, make sure input logging is turned on in the diagnostic settings. This will ensure that all incoming request data is captured in the logs going forward.