# Deployments REST API error details

**URL:** <https://forum.flowable.org/t/deployments-rest-api-error-details/6721>\
**Category:** Flowable Engine\
**Created:** [September 15, 2020, 9:53am UTC](https://forum.flowable.org/t/deployments-rest-api-error-details/6721 "2020-09-15T09:53:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mikezerosix](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/mikezerosix/32/2160_2.png) [@mikezerosix](https://forum.flowable.org/u/mikezerosix)\
**Post date:** [September 15, 2020, 9:53am UTC](https://forum.flowable.org/t/deployments-rest-api-error-details/6721/1 "2020-09-15T09:53:07Z")

</div>

When deploying using REST API and there is an error in one of the models the REST API just returns “HTTP 500” which is not very usefull.

You have to have access to the application log fils to dig up the reason like:  
“XMLException: cvc-complex-type.4: Attribute ‘sourceRef’ must appear on element ‘sequenceFlow’”  
and the stack trace even has the xml line number for the error. This is information absolutely crusial to the person uploading the deployment.

Is there a way to configure deployments REST API to include the Java exception stack trace in error response body ? Spring usually does this by deafult.

---

<div class="post-metadata">

**Author:** ![mikezerosix](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/mikezerosix/32/2160_2.png) [@mikezerosix](https://forum.flowable.org/u/mikezerosix)\
**Post date:** [September 18, 2020, 10:15am UTC](https://forum.flowable.org/t/deployments-rest-api-error-details/6721/3 "2020-09-18T10:15:31Z")

</div>

Turns out our solution ate the message which there is with good details.