Getting a 500 when post some raw json to a triggered pipeline

To fix this I dropped off a JSON parser snap that was sitting in front of a copy, the copy is now the first snap in the pipeline with an open input and I’m no longer getting the 500 error.

@AdrianH, when open the trigger task url with a browser, the browser is making a HTTP GET request. GET request doesn’t submit a request body. Postman can do POST request with a body.

For this 500 status case, what do you see in the pipeline run log?

This is likely the first snap in the pipeline failing due to no input - as per @eguo’s response, you’re not Posting anything when you do it through the browser.

Would be good to see the pipeline logs and the pipeline itself to confirm, however.

Here’s my latest effort, I cut down the json to something a little more manageable :

{“Sourceidentification”:{“countryid”:“AAA”,“areaname”:“Somewhere”,“systemname”:“TOffice”},“Filemetadata”:{“rowcount”:“320”,“checksum”:“9424ADEABBFC7DFE7AF18DFFCB97C0FE”},“measurements”:{“distance”:[{“vehicleid”:“AB123CD”,“value”:“123456”,“document”:“20160419141000”,“date”:“2016-04-18”,“Time”:“”}]}}

{
“query_string”: “”,
“path”: “/api/1/rest/slsched/feed/xxxxxx/xxx/xxxxxxxxx/Measurements”,
“response_map”: {
“error_list”: [
{
“message”: “Pipeline failed to execute.”
}
]
},
“http_status”: “500 Internal Server Error”,
“http_status_code”: 500