Flow
Flow step is skipped due to unrecognized UI element
Issue
- The Flow skips at step 1 and continues from step 2 because the UI element of the application at step 1 is visible only on a minimized screen and not on the full screen mode.
Probable Causes
- The application uses a responsive design, which adjusts the visibility of UI elements based on the browser’s dimensions.
- The application loads slowly.
- The first step of the flow is marked as optional due to which the flow step skips and moves to the next step.
Suggested Solutions
-
Add a unique CSS Selector to specifically target the UI element. For more information, see Identify an element's CSS selector.
-
If the first step of the Flow is optional, enable the Always start this flow on step one toggle option. For more information, see Always start a Flow from step 1.
If the issue persists, contact support@whatfix.com.