Flow Failure Reason - Element could not be found
- 18 May 2023
- 1 Minute To Read
-
Print
-
DarkLight
-
PDF
Flow Failure Reason - Element could not be found
- Updated On 18 May 2023
- 1 Minute To Read
-
Print
-
DarkLight
-
PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Issue
Flow has failed because 'Element could not be found because some of the original properties of the element captured while creating the content have changed.'
Cause
Following are some potential cases where a Flow might fail because 'Element could not be found because some of the original properties of the element captured while creating the content have changed.'
- Whatfix was unable to detect the element on which the Flow step was created.
- The application UI over which the step was created may not be the same as the one over which the Flow is played.
- The configured CSS Selectors don't point to the correct element or are unable to identify the element. For more information, see How to find the CSS Selector of an element using Whatfix Studio?.
- If the Flow was created a long time ago, the properties of element structure may have changed. Re-selecting the failed steps ensures that the Flow doesn't fail. For more information, see Reselect Elements to manage UI changes.
Solution
- Verify and/or reselect the element on which the Flow is breaking.
- In case of a discrepancy, re-select the element or verify the CSS selectors on which the step is failing. For more information, see Reselect Elements to manage UI changes.
Was this article helpful?