- 02 Sep 2022
- 2 Minutes To Read
Flow does not run correctly
- Updated On 02 Sep 2022
- 2 Minutes To Read
Flows are displayed based on the visibility rules that are set up when creating the Flow. If a Flow fails at a certain step, it is usually because of one of the following reasons:
- The conditions required to show the next step have not been met
- Your application has changed, and the element necessary to display the next step is not getting detected
There may be many reasons why your Flow is not working. Listed below are a few reasons and some solutions that you could try to fix the issue.
- Something may have changed in the underlying application, and Whatfix is unable to find the element that was selected when the Flow was created.
- The step conditions for the Flow may be incorrect or the step may be optional and the conditions don't match.
- For example, one of the reasons could be that the step condition is being evaluated while the page is still loading. So if you are using the on-click of element visibility rule, try switching to the on page refresh rule.
For more information, see Step completion rules.
- The Flow may have been created in a non-production environment but is being run in the production environment.
- The application may be taking time to load and the visibility rule that determines the content display may not be optimized. For example, the rule may be set to be triggered by the on click of the selected element because the page has not refreshed, the element that is supposed to trigger the next step has not yet been displayed, and thus, the step does not display.
- Element IDs are different in UAT and Production and the account has been configured to Trust IDs
- There may be a conflict in the configuration and the Flow may not be displayed on the intended page.
- Navigate to the step that is not working and try reselecting the step.
- Verify if the step conditions for the failed step are correctly configured.
- Ensure that the Flow was created in an environment identical to what you have in production. The element attributes in production are often different compared to the attributes in UAT.
- If the Flow was created in a UAT environment, and the account has been configured to trust IDs, ensure that the IDs are the same in both environments.
- If you are facing issues with Smart Context enabled accounts, contact [email protected] to troubleshoot further.