In the Flow UI you can now view and edit snapshot of the trigger. Snapshot management is accessed via Advanced Settings in Step summary:
Then you get to snapshot manager itself:
You can now use Advanced Settings section in Step Summary tab to configure prefetch.
Note: the changes will be applied after clicking the Finish step button.
There is now a limit that defines the maximum number of errors we list for a Flow. If the limit is reached, no new errors are listed for the given Flow anymore. This new limit will protect you from the “chatterbox” Flows that tend to spam too much.
New MAX_ERROR_RECORDS_COUNT
environment variable was added. If the amount of
errors per Flow gets higher then MAX_ERROR_RECORDS_COUNT
value, we remove old
error records and show corresponding notification in UI.
Also, we added a new k8s CronJob remove-excess-error-records
. This job is
clearing oldest flow error records if they are exceeding limit. The default limit
is 1000
records per Flow, and is set by MAX_ERROR_RECORDS_COUNT
environment variable.
Automatic conversion of raw XML files on Webhook is toggled in component.json
with consumesRawData
flag. If true
, then Webhook will not convert incoming data to JSON
.
Added better tool-tips for mapping modes in the new mapper.
INTERNAL - Flow Suspended
was added to the segment.io, so we can better track
Flows suspension process.
You can now configure step message prefetch count through the API. We added a
new prefetch
field as a parameter to nodeConfig
section of the /v2/flows
endpoint. The mapper-step gets the same prefetch as the previous step.
EXAMPLE:
"attributes": {
"nodes_config": {
"step_1": {
"prefetch": 4
}
}
}
}
The default number of logs displayed per page is 200
. You can set this number to: 400
, 600
, 800
or 1000
.
New emails are sent in case of events of the following scales:
elasticio-sailor-nodejs@2.6.4
is required).refresh_token
are now marked as invalid.Create Order
Lookup Object By ID
to allow lookup of Orders By External IDGet Objects Polling Trigger
for “Time stamp field to poll on”refresh_token
will now be marked as invalidrefresh_token
and emits an error in case it is not validlookup object
actionLookup Objects ( at most 1 )
now works for date or date-time field types