Skip to content

Handling http response not convertible to workflow model #1242

@fjtirado

Description

@fjtirado

If the http response is not convertible to Workflow Model (because unexpected content type response or because it is not a json one), currently a runtime exception is thrown.

It would be better to convert that runtime into a DATA workflow error, which will allow users to ignore it by catching in the workflow definition (for example if they are not really interested in the service response)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions