Source: https://nishanth-fern-test.docs-staging.pageloop.ai/web/flow-fails-with-alternating-steps

# Error: Possible issue with step type

#### Issue

A Step-by-Step Flow stops or fails to show the next instruction when a **Free-floating** step type is immediately followed by an **Attached to element** step type Flow on a different screen. You see the following error message: **Possible issue with step type**.

![Possible issue with step types in Flows](/images/2f/Studio_Flows_possible-issue-with-steps-2f4b5270.png)

#### Probable Cause

**Step type conflict across pages**: The Flow sequence includes a **Free-floating** step followed by an **Attached to element** step, and these two consecutive steps are configured on different pages. For example, if a **Free-floating** step (Step 1) is on Page A, and the next step (Step 2), which is **Attached to element**, is on Page B, the Flow will break if the user doesn't perform the action needed to move from Page A to Page B. This means if the user clicks **Next** instead of clicking the UI element on page A, the Flow breaks. ![Step type issue in Flows](/images/19/Studio_Flows_stepissue-19f2aaaf.png)

#### Suggested Solution

**Keep the consecutive steps on the same screen of your application only while switching steps:** When creating a Flow, ensure that an **Attached to element** step type that comes immediately after a **Free-floating** step is set up to appear on the same screen. The application runs checks to ensure it alerts you if it finds any consecutive steps that might break the Flow because they are on different screens. If you get an alert, you should either move the steps so they are on the same screen. In case you feel the Flow won’t fail, you can ignore the alert messages.

> [!WARNING]
>
> If the issue still persists, contact [support@whatfix.com](mailto:support@whatfix.com?subject=Error%3A%20Possible%20issue%20with%20step%20type\&body=Hi%0A%0APlease%20help%20me%20fix%20this%20error%3A%20Possible%20issue%20with%20step%20type%20while%20using%20Flows.%20%0A%0AThanks%0A).
