Version 19.51 is full of new stuff!

NOTE: From this release we have adopted new release numbering format based on year and week of the release - YY.WW. YY are the last two digits of the year, and WW is the number of the week in that year. Following this template, our current release is 19.51.


You can now retry failed messages using the new feature called Retry. Any error emitted by a component can be retried if the flow is active. Error or success entry appears in the current Runlog execution. Feature details can be found here:

Retry feature in action

Also, now you can filter mapping view to see mandatory fields and hide optional fields:

Hiding optional fields


You can now disable the passthrough for a selected flow step using an API call to the following endpoint:

PATCH /v2/flows/:id

NOTE When the passthrough is disabled for a step, the platform would reset all the data from the previous steps and start again collecting the data from the steps from that step only.

This feature is available via an API call only. More details here.


Order of fields in component descriptor

Now you can configure the order of fields in component.json using the new numeric key order for:

  • output metadata
  • credentials
  • action/trigger
  • action/trigger order
  • action/trigger on recipe activation page
  • credentials on recipe activation page

Ordering fields in component.json

For more details read the component descriptor ordering fields document.

Custom scripts for individual tenants

Additionally, custom scripts for individual tenants can run on every page before authorization:

  • Login pages
  • Forgot password pages
  • Register pages
  • Reset password pages
  • Invite page

Little bits

  • Component environment variables can have global visibility again.
  • The deprecated links links.documentation and tenant.links in the tenant description body are no longer supported.

List Of Fixed Bugs

We were totally dedicated to improvements this month, so all the discovered bugs were immediately fixed before going into production.

Technical Details
Go to Details →

API Stuff

Schema of the passthrough toggling request body:

    "data": {
        "type": "flow",
        "id": "5de7d63a944b750013fb3f09",
        "attributes": {
            "nodes_config": {
                "step_2": {
                    "passthrough": {
                        "disabled": true