The Flow Start Log helps you understand when, how, and by whom flows are started in your workspace. It’s especially useful for auditing large launches, troubleshooting unexpected activity, and comparing intended audiences to actual flow runs.
In this guide, you’ll learn where to find the Flow Start Log, what each entry contains (flow name, started by, start date, contacts/groups selected, completed runs), and how to interpret cases where run counts are lower than expected.
When you manually start a flow, the Flow Start dialog includes “sending options” checkboxes that help you control which contacts are included or excluded. These options reduce risk when launching flows at scale by preventing interruptions, targeting recently active contacts, and avoiding repeated participation.
In this guide, you’ll learn where to find sending options, what each checkbox does (Active contacts, Skip contacts currently in a flow, and Inactive contacts), and how to combine them for safer, more precise flow starts.
Labels help you keep large workspaces tidy by grouping related flows (by project, campaign, or purpose). By applying the same label to multiple flows, you can quickly filter the Flows list, separate test flows from production, and help teammates find the right flows faster.
Flows are how you automate conversations in RapidPro.app. In a flow, you build steps (messages, questions, decisions, updates) that guide contacts through a structured interaction. Creating a flow is the first step before you can test logic, connect triggers, or launch to real users. In this guide, you’ll learn how to create a new flow […]
6–8 min read Flows Updated on: 18/12/2025 Set up a clean A/B test in minutes If you just need the essentials, use this as your fast path: Define what you’re testing and the success metric Add Split Randomly and name categories clearly Build each variant branch (keep differences minimal) Track assignment (group, field, or label) […]
“Split by Contact Field” helps you decide what to do next based on what you already know about a contact. It’s especially useful for avoiding repeated questions (like asking for a name every time) while making sure missing fields get collected and stored when needed.
To message a group of contacts, create a simple flow that contains a Send Message action, then Start that flow for one or more groups. This approach gives you control over who is included (recent activity, not already in a flow, not recently started in the same flow), and it lets you monitor large sends and delivery progress via the Flow Starts page.
When you manually start a flow, the Flow Start dialog includes contact inclusion options that help you target the right audience. You can limit starts to recently active contacts, exclude contacts already in another Messaging flow, and avoid restarting contacts who entered the same flow recently. These filters can be combined, and the contact counter updates instantly to show how many contacts will actually be started.
Copying a flow is the safest way to reuse logic without risking changes to your original. You can duplicate an existing flow to create a new version, test improvements, localize content, or build a new workflow using the same structure. In this guide, you’ll learn how to create an exact copy of a flow, quickly […]
Introduction: Flow expirations help you keep runs clean when contacts stop responding or get stuck in loops. By setting an expiration, you automatically remove inactive contacts after a defined period—so your flow doesn’t stay “open” forever and your reporting stays meaningful. 6–8 min read Flows Updated on: 18/12/2025 Expire inactive runs (and keep reporting clean) […]
