Start Strong
Sell Smart
Manage with Ease
Market to Success

Common Issues Related to Flow Configuration

What conditions should be considered when configuring Flow Automation app?

Some merchants question why they can’t use Flow in their stores. If there is a running record in your Flow process but no action was taken, refer to the article below to confirm the problem.

 

 

Verifying Trigger Configuration

  • Verify whether filtering conditions are enabled for triggers.
    • If filtering conditions are enabled, a process will be triggered only when a scene occurs and the filtering conditions are met. If filtering conditions are set strictly, the probability of triggering a process is likely to be low.

 

 

Verifying Condition Configuration

  • Verify whether the relationship between conditions is configured correctly.
    • In the case of multiple conditions, they can be configured as all conditions are met at the same time or one of them is met. Therefore, please confirm whether this relationship is configured correctly.
    • If the condition you select is a list of data (which may contain multiple rows of data), you can configure the following: conditions are met by all data in the list; conditions are met by any row of data in the list; or none of the rows meet the conditions. Therefore, please confirm whether this relationship is configured correctly.
  • Verify whether the condition-matching mode is correctly configured. The following four expressions can be easily confused:
    • Equal: Only one expected value can be entered, and the actual value should match exactly the expected value. Take the figure on the right as an example. The SKU item number must be exactly the same as the value you enter so that they’re considered a match.
    • Equal to any of the values: You can enter multiple expected values, and there will be a match if the actual value equals any of the expected values.
    • Not equal to: Only one expected value can be entered, and it is considered a match if the actual value is not exactly the same as the expected value. Take the figure on the right as an example. If the SKU item number is slightly different from your entered value, it’s considered a match.
    • Not equal to any of the values: You can enter multiple expected values, and it is considered a match if the actual value doesn’t fall in the expected value range.
  • Verify whether the expected value of the condition is too high.
    • When the expected value of the condition is high, most processes can’t proceed because the conditions can’t be met.
  • Verify whether the variable parameters used in conditions are configured correctly.
    • Variable parameters may be used in the expected value of conditions. Make sure the variable you are using is the information you want, otherwise, there may never be a match.