Skip to main content
Flows are the heart of Autosana. A flow is a test written in natural language that describes what you want your agent to do in your app or website.

​
What is a Flow?

A flow is a set of instructions that the agent follows to interact with your app or website. Instead of writing code or recording clicks, you simply describe what you want to test in natural language. Example Flow:
The agent interprets these instructions, finds the relevant UI elements, and executes a series of actions, verifying results at each step.

​
Creating a Flow

​
Method 1: Quick Create

  1. Navigate to the Flows page
  2. Click Create Flow
  3. Enter a flow name (required)
  4. Write your instructions in natural language
  5. Click Create Flow

​
Method 2: Create in Suite

Create a flow directly within a suite:
  1. Navigate to the Flows page
  2. Expand a suite
  3. Click Create Flow within the suite
  4. Follow the same steps as Quick Create
  5. The flow is automatically added to the suite

​
Method 3: Define in Your Repo

Keep flows in version control and sync them from your repository — see Code-Managed Flows.

​
Writing Effective Flow Instructions

See Writing Effective Flow Instructions for guidance and examples.

​
Supported Agent Actions

Universal Actions (work on both mobile and web): Mobile-Only Actions: Web-Only Actions:

​
Running Flows

​
Running a Single Flow

  1. Find your flow in the Flows table
  2. Click the Play button (▶️)
  3. Select your app
  4. Click Run Flow

​
Running Multiple Flows

Select multiple flows using checkboxes:
  1. Check the boxes next to flows you want to run
  2. Click Run Selected in the floating action bar
  3. Select your app
  4. Click Run Flows
Shift-Click Selection: Hold Shift and click to select a range of flows quickly

​
Auto-Retries

Autosana can automatically re-run a failed flow before reporting it as failed. Configure this in Settings → Agent.
  • Retries: Set how many times a failed run is retried (0–5, default 1). A flow is only marked failed after all attempts are exhausted — if any attempt passes, the flow is reported as passed.
  • Intelligent Retries: On by default. Retries are focused on flows with a track record of passing; flows that are consistently failing aren’t retried. Turn it off to retry every failure.

​
Managing Flows

​
Editing a Flow

  1. Click the pencil icon (✏️) next to a flow or click on the flow row
  2. Modify the name or instructions
  3. Click Save Changes

​
Viewing Version History

Flows maintain a complete version history:
  1. Click Edit on a flow
  2. Click the Version History tab
  3. View all previous versions with timestamps
  4. Click Revert to restore a previous version

​
Duplicating a Flow

To create a copy of an existing flow:
  1. Click the three dots (⋯) next to a flow
  2. Select Duplicate
  3. A copy is created with “(Copy)” appended to the name
  4. Edit the duplicate as needed

​
Deleting a Flow

  1. Click the three dots (⋯) next to a flow
  2. Select Delete
  3. Confirm deletion

​
Organizing Flows with Suites

Suites help you organize related flows and run them together.

​
Adding a Flow to Suites

Method 1: During Creation
  • When creating a flow, select which suites it should belong to
Method 2: After Creation
  1. Click the three dots (⋯) next to a flow
  2. Select Attach to Suite
  3. Check the suites you want to add the flow to
  4. Click Save
Method 3: From Suite View
  1. Expand a suite
  2. Click Add Existing Flows
  3. Select flows to add
  4. Click Add Flows

​
Removing a Flow from a Suite

  1. Expand the suite containing the flow
  2. Click the three dots (⋯) next to the flow
  3. Select Remove from Suite
  4. Confirm removal

​
Flow Status and Results

​
Status Types

​
Viewing Results

Click on any status badge to view detailed results:
  • Screenshots: Visual snapshots at each step
  • Action Log: Every action performed by the agent
  • Errors: Any issues encountered
  • Timeline: Duration of each step
  • Device Info: Device type and OS version used

​
Advanced Features

​
Attaching Files

Attach reference images to your flow instructions:
  1. Click the paperclip icon (📎) when creating/editing a flow
  2. Select files to attach
  3. Reference the files in your instructions: “Open the gallery and tap on ${file:smiley_face.jpg}”

​
Using Hooks

Hooks are reusable scripts that run before or after your flow: Setup Hooks: Run before the flow (e.g., “Clear app data and restart”) Teardown Hooks: Run after the flow (e.g., “Logout and clear cache”)
  1. Click Edit on a flow
  2. Click Add Hook
  3. Select Setup or Teardown
  4. Write the hook instructions
  5. Save the flow
You can read more about hooks here.

​
Run Caching

When enabled, flows that have previously passed will use cached action sequences for faster execution (5-8x speedup). Run caching is best-effort and enabled by default. How it works:
  • After a flow passes successfully, the action sequence is cached
  • Subsequent runs replay the cached actions with a smaller, faster model
  • If the replay fails (e.g., due to UI changes), the full agent takes over
Manage it in Settings → Agent Features.

​
Troubleshooting

​
Flow Fails Immediately

Possible Causes:
  • App build is missing or corrupted
  • Bundle ID mismatch
  • App crashes on launch
Solutions:
  • Check that your app has an active build
  • Verify the bundle ID is correct
  • Test the app build manually first

​
Agent Can’t Find Elements

Possible Causes:
  • UI element description is ambiguous
  • Element isn’t visible on screen
  • Element loads after a delay
Solutions:
  • Disambiguate by purpose or nearby label rather than visual attributes. Prefer “Tap the ‘Submit’ button under the password field” over “Tap the blue submit button in the bottom right” — describing pixel position or color locks the test to today’s UI.
  • Add a wait when the element loads asynchronously: “Wait for the order summary to appear, then continue.”

​
Next Steps