Jump to
Product Updates
v24.45 v24.40 v24.36 v24.27 v24.23 v24.17 v24.13 v24.09 v24.05 v24.01 v23.48 v23.44 v23.39 v23.31 v23.27 v23.27.1 v23.24 v23.19 v23.19.1 v23.14 v23.14.1 v23.12 v23.10 v23.08 v23.06 v23.04 v23.02 v22.52 v22.50 v22.48 v22.46 v22.44 v22.42 v22.40 v22.38 v22.36 v22.34 v22.32 v22.30 v22.28 v22.26 v22.24 v22.22 v22.20 v22.18.1 v22.14 v22.12 v22.10 v22.08 v22.06 v22.04 v22.02 v21.51 v21.49 v21.47 v21.45 v21.43 v21.41 v21.39 v21.37 v21.35 v21.33 v21.31 v21.27 v21.23 v21.19 v21.14 v21.10 v21.06 v21.02 v20.51 v20.47 v20.43 v20.39 v20.35 v20.31 v20.27 v20.23 v20.19 v20.15 v20.11 v20.07 v20.03
Updated on

Product Update - v22.16

Details of the product update v22.16 from 21st of April 2022.

Improvements and Updates

Not enough quota to start task

If you are one of our many power users you might have noticed from time to time a pop-up warning with a message Not enough quota to start task. These messages were not related to your RAM quota limit. Instead these messages are triggered by real-time flows with more than 25 steps. Because the platform initiates each step sequentially, these errors are triggered when all flow steps cannot be initiated within the allowed time.

We have resolved this issue by ensuring that all steps (Kubernetes pods) are initiated in parallel, thus significantly shortening the time required to start the flow. We also changed the warning message to The flow FLOW NAME (FLOW ID) is taking longer than expected to transition.

Example of error

News in this section are for our customers who use OEM version of the elastic.io platform.

Enforce 2FA use

Tenant administration can now enforce the 2FA during the login. We introduce a tenant configuration flag called forced_totp to switch this feature on.

  • To enable forced_totp you must enable the enabled_totp as well.
  • If you remove the enabled_totp feature flag, system will remove forced_totp as well.

You can set these parameters either during the tenant creation or you can update the parameters of an existing tenant via an API call. An example of such an API call is shown below.

{
  "data": {
    "type": "tenant",
    "attributes":{
      "feature_flags": {
        "enabled_totp" : true,
        "forced_totp" : true
      }
    }
  }
}

From 22.16 version, the platform checks status of the forced_totp parameter during your navigation of every page in the UI. If tenant administration enforced the 2FA and you have not enabled the 2FA for your account then you will be redirected to your profile page and presented a pop-up form to enable the 2FA.

Enable 2FA

Fixed bugs

  • Changed the platform behaviour when webhook would give an error when an integration flow would have adding a step after the request-reply component in the WebHook -> Request-reply flows.

Components

Hubspot component 1.5.2

  • FIXED bug connecting with the uploading attachments

Salesforce component 2.2.3

  • UPDATED dependencies and addressed the packaged vulnerabilities

Sftp component 1.4.7

  • FIXED uploading the attachments

Zendesk component 1.0.1

  • UPDATED Sailor version to 2.6.27
  • UPDATED dependencies and addressed the packaged vulnerabilities
  • ADDED the component pusher job to Circle.ci configuration.
  • UPDATED component-commons-library version to 2.0.2
  • FIXED the attachments processing

Email component 1.0.14

  • UPDATED Sailor version to 2.6.27
  • UPDATED dependencies and addressed the packaged vulnerabilities
  • ADDED the component pusher job to Circle.ci configuration.

CSV component 3.1.2

  • UPDATED the component-commons-library to read and upload attachments through the Maester service
  • UPDATED Sailor version to 2.6.27
  • UPDATED dependencies and addressed the packaged vulnerabilities

Request-reply component 1.2.3

  • UPDATED Sailor version to 2.6.27
  • UPDATED dependencies and addressed the packaged vulnerabilities
  • ADDED the component pusher job to Circle.ci configuration.