What a Flow Contains
Every flow is made up of one or more steps. Each step represents a single user action or assertion. You can combine these step types in any order to model any real-world interaction:Flow Status
Every flow in your dashboard has a status that reflects its most recent run result:- Passing — The flow completed every step successfully on its last run. Your feature is working as expected.
- Failing — One or more steps failed on the last run. TYAN records which step broke, the error message, and a screenshot of the failure state.
- Never Run — The flow has been created but has not been executed yet. Run it manually or attach it to a monitor to get a live result.
Flows run against your live production URL by default. You can override the base URL per flow to target a staging environment, a preview deployment, or a branch URL — useful when verifying a feature before it ships.
Example: Signup Flow
Here is what a typical signup flow looks like when broken into steps:- Navigate to
https://yourapp.com/signup - Fill the Email field with
test@example.com - Fill the Password field with a test password
- Click the Create Account button
- Assert text “Welcome to YourApp” is visible
- Assert URL matches
https://yourapp.com/onboarding - Take screenshot
Related Concepts
Journeys
Chain multiple flows together into a complete end-to-end user path from entry to conversion.
Monitors
Schedule any flow to run automatically and get alerted the moment it breaks in production.