Optimizing Odoo Lookup & Destination calls

If you have a scenario where your Odoo flows (using Odoo lookups and / or destination) are taking an inordinate amount of time to complete, or worst case, experiencing flow timeouts, there some optimizations we can make.

Typically, this is most prevalent when syncing a large buffer or dataset to Odoo (e.g. several thousand records).

By default, the Odoo lookup and destination step are set with 1 concurrent call. Additionally for the Odoo lookup specifically, the calls run in series and caching is not enabled.

Note regarding caching - this will only have a tangible impact when dealing with codes (e.g. postal codes). It will have less impact when dealing with account details as these are natively always unique.

In order to adjust these settings,

  1. Navigate to the Odoo lookup step in your flow and click edit.
  2. Click on Advanced Settings (top left).
  3. Adjust the values as illustrated below to preference. Noting the concurrent calls listed below are an example (20) and can be adjusted an tweaked based on metrics and results.

image

To make this change on the Odoo destination step,

  1. Navigate to the Odoo detination step in your flow and click edit.
  2. Click on Advanced Settings (top left).
  3. Adjust the values as illustrated below to preference. Noting the concurrent calls listed below are an example (20) and can be adjusted an tweaked based on metrics and results.

image