Introduction: Flow results help you understand what’s happening inside your automation: who responded, what they answered, and where drop-offs occur. In RapidPro.app, you can open a flow’s Results view to monitor engagement, review analytics, and inspect individual runs.
Read results fast (spot drop-offs and debug runs)
If you just need the essentials, follow this quick path:
- Open Results from the flow editor (☰ menu → Results)
- Learn the Results layout (Overview / Engagement / Analytics / Runs)
- Use Overview to monitor completion and run statuses
- Use Analytics to evaluate questions and “Other” rates
- Use Runs to inspect real contact journeys and exit reasons
These views help you measure performance and troubleshoot issues with real data.
Step-by-Step Process
- Go to Flows and open the flow you want to analyze.
- In the flow editor, click the ☰ menu (top-right).
- Select Results.
[CAPTURE: Flow editor showing the ☰ menu expanded with “Results” highlighted.]
On the Results page, you typically have:
- A Download button (export results)
- Tabs such as Overview, Engagement, Analytics, and Runs
[CAPTURE: Results page header showing tabs (Overview / Engagement / Analytics / Runs) and a visible Download button.]
In Overview, you’ll usually find:
- Responses received per day
- Completion rate across runs
- Run statuses (completed, ongoing, expired, interrupted)
- Patterns by day of week and time of day
[CAPTURE: Overview tab showing a responses-by-day chart and summary metrics (completion, ongoing, expired, interrupted).]
In Analytics, you can break down responses per collected field/result (examples: name, age, gender). This helps you see:
- Which answers are most common
- Where “Other” responses appear often (possible confusion)
- Which questions might need clearer wording or better response rules
[CAPTURE: Analytics tab showing result fields (e.g., “name”, “age”, “gender”) and their response breakdown.]
In Runs, you’ll see:
- Each contact who interacted with the flow
- How many times they ran the flow
- How/when they exited the flow
Contacts can exit when they:
- Complete the final node
- Start another flow (via “Start/Enter another flow” actions)
- Expire due to inactivity (flow expiration settings)
[CAPTURE: Runs tab listing contacts and run counts, with a detail view showing run status and exit reason.]
Common Issues & Quick Fixes
I don’t see results changing after edits
Problem: You updated a flow and expected older runs to reflect the new logic.
Fix: Results reflect what happened during runs. Use Runs to compare older vs newer runs, and confirm contacts are entering the updated version of the flow.
Completion rate dropped suddenly
Problem: Fewer contacts reach the end than before.
Fix: Check Overview for the date the drop started, then open a few recent Runs to see which node/category is causing the exit (timeouts, “Other”, channel delivery issues).
Too many “Other” answers in Analytics
Problem: Valid answers aren’t matching your categories.
Fix: Improve prompts with examples, expand synonyms in response rules, and keep the catch-all “Other” last so specific matches win first.