Rest broker tries to populate smart object on 400 response

  • 2 December 2020
  • 0 replies

We have a smartobject in our workflow that is a rest broker to an external service.  When the external service returns a 400, the smart object still attempts to populate the object.  In our case, this generates an unhandled error in our workflow (String was not recognized as a valid Boolean).  We are sure it is the smartobject as it doesn’t error out if we change the parameter type to text.  It makes no sense to have to change your parameter types to be able to handle error conditions.  Are we not implementing this correctly or is this a K2 limitation?

Our swagger file has both 200 and 400 responses defined.  The 200 response contains a couple of boolean parameters.  The 400 response has no content.

0 replies

Be the first to reply!