Skip to content

Handling http response not convertible to workflow model #1242

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)

Activity

  1. self-assigned this
    on Mar 18, 2026
  2. added 5 commits that reference this issue on Mar 18, 2026
    79d735e
    fddf383
    294d09b
    db511af
    2124d00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions