Skip to main content
Question

Error handling when releasing move entry through REST API

  • December 19, 2025
  • 2 replies
  • 10 views

We are using the “entity/Manufacturing/23.200.001/MoveEntry/ReleaseMoveEntry” REST API Endpoint to release the move entry at the end of the process.  We get a 202 Accepted response even when the release was unsuccessful.  A couple of reasons for the release being unsuccessful is duplicate serial numbers being received and backflush not being setup properly in the BOM.  In both of these scenarios, we still receive the 202 Accepted response with no body.  How can we “trap” these errors so we can report them to users to make the corrections?  Is there a different API call to use?  Any thoughts would be appreciated.

Thank you in advance.

2 replies

Forum|alt.badge.img+7
  • Captain II
  • December 19, 2025

That’s odd that the error isn’t being relayed back. I’d report that as a bug.

With regards to knowing if the transaction actually released or not, you could query the transaction and check the status. If it hasn’t changed then you can let the user know that someone will have to review the transaction manually.

Something you might be able to try is to wrap the release in your own logic around the release logic. If you can test for the errors, you can look at providing a more meaningful error to the end user.


  • Author
  • Freshman I
  • December 19, 2025

Thank you very much for your response. We’ll report this as a bug. 
It looks like we can do a GET request to get the status of the transaction and if it’s not released throw an error. At that point, it sounds like we’ll have to manually check the logs to see why it failed.

We’ll see what else we can do to get a more meaningful error.

Thanks again.