Guide: Why a condition took its way
This page: https://commentwatchdog.com/help/flow-conditions/why-a-condition-took-its-way
Topic: Conditions
Time: about 2 minutes
Who can do it: Owner, Administrator or Manager
Author: https://anantgupta.xyz (Anant Gupta, founder of CommentWatchDog)
Start in the app: https://app.commentwatchdog.com/en/inbox
Result when done: You can see which check decided for one person.
Context: Every run keeps what each step read and decided. For a condition, that is each rule with what it read and its verdict, and the way the person went. When someone took the No way and you expected Yes, the run says why.

Before you start:
1. Runs appear once the flow is saved and someone goes through it.
2. The newest runs keep every detail; older ones keep their path.
3. Opening a run lays its path over the canvas.

Steps:
Step 1 of 3: Open Runs on the flow.
Where: The bar at the top of the flow: Runs. The panel lists runs still going first, then finished ones. The chips above the list filter it: All, Still going, With your team, Finished, and Failed or Skipped when there are any.
Link: https://app.commentwatchdog.com/en/inbox (Open the app)
Screenshot: https://commentwatchdog.com/media/shots/dm-flow-history.en.webp (Runs on the bar; the runs panel opens on the left.)
Screenshot: https://commentwatchdog.com/media/shots/dm-flow-history-phone.en.webp (On a phone, Runs is the clock button in the bar, lit while the list is open; the chips that filter the list are under its title.)
You should see: One row per run, with who and when.

Step 2 of 3: Open one run.
Where: Click the run in the list. Its steps open under it, numbered in order, and its path lights up on the canvas; a step it did not reach says This run didn't reach this step.
Screenshot: https://commentwatchdog.com/media/shots/dm-flow-run.en.webp (One run open: its steps in order, and its path on the canvas.)
Screenshot: https://commentwatchdog.com/media/shots/dm-flow-history-phone.en.webp (On a phone: tap a run and its steps open under it, numbered in order.)
You should see: The steps of this run, numbered in order.

Step 3 of 3: Read the condition's rules.
Where: Click the condition in the run's steps. Its settings open with In this run on top: Every rule had to match, or One matching rule was enough, then each rule with its verdict: Matched, Didn't match, Not checked (the answer was already decided), or Unknown (Instagram didn't share it, so it didn't match). Went on by names the way, Yes or No.
Screenshot: https://commentwatchdog.com/media/shots/dm-flow-run.en.webp (In this run: each rule and its verdict; Went on by No.)
Screenshot: https://commentwatchdog.com/media/shots/dm-flow-run-rules-phone.en.webp (On a phone: tap the condition in the run's steps; its sheet opens on In this run.)
You should see: Each rule with its verdict, and Went on by with the way this person took.

If something is off:
Problem: No runs yet
Fix: Runs appear once the flow is saved and someone goes through it. Test it on your own account first.
Problem: This run's step details were trimmed
Fix: Older runs keep only their path; the newest runs keep every detail.

Common questions:
Question: Why does a rule say Not checked?
Answer: With Needs every rule, the condition stops at the first rule that fails; with Needs any one rule, at the first that holds. Rules after that are not checked.
Question: What does Unknown mean?
Answer: Instagram did not share the answer, so the rule did not match, either way round.

Related guides:
- How a condition works: https://commentwatchdog.com/help/flow-conditions/how-a-condition-works
- Check their Instagram profile: https://commentwatchdog.com/help/flow-conditions/check-their-instagram-profile
- Runs: what each automation did: https://commentwatchdog.com/help/keyword-automations/runs-what-each-automation-did

Plain text of this guide: https://commentwatchdog.com/help/flow-conditions/why-a-condition-took-its-way.md
All guides for assistants: https://commentwatchdog.com/help/llms.txt