Runs: what each automation did

For any comment or message, you can see what the automation did, step by step, with the exact messages.

By Anant Gupta, founder3 min readOwner, Administrator or ManagerUpdated

Copies the whole guide as plain text, with every location and link, to paste into an assistant.Open in the app
On this page
  1. Before you start
  2. 1Open Runs from an automation's menu
  3. 2Read a run's row
  4. 3Filter to the runs that need you
  5. 4Open a run
  6. 5Open the chat it belongs to
  7. If something is off
  8. Common questions
  9. Related guides

Before you start

  • 30 / 90 days; the counts stay.
  • Needs a person: act.
  • New runs arrive on their own.
Steps

Open Runs from an automation's menu.

A rowthe three dotsSee runs

See runs, in a row's menu.
See runs on a phone.

You will see The Runs page.

Read a run's row.

WhenPersonWhat happenedthe outcome

One run: when, who, which automation, and what happened.
A run's row on a phone.

You will see Day groups, one pill per run.

Filter to the runs that need you.

AllNeeds a personSkipped

Needs a person, with its count.
The same filter on a phone.

You will see Only the runs that need someone.

Open a run.

A rowthe run's steps

A run, opened: each step with its time and the message as sent.
A run on a phone.

You will see The exact messages.

Open the chat it belongs to.

The runOpen the thread

Open the thread, at the bottom of the run.
Open the thread on a phone.

You will see The chat in Messages.

If something is off

A run says Waiting
Waiting: Requests, or no tap yet.
A run says Failed
Failed: the row says why.
A run says Skipped
Skipped: the reason is on the row.
A person is shown as Forgotten person
Forgotten: the runs stay nameless.

Common questions

Do new runs appear on their own?

Yes, the page checks every 20 seconds and lands new runs at the top with a soft highlight.

Can I search runs by the person?

Yes, by the username or name; press / to jump to Search people.

How long are runs kept?

Skipped runs are kept 30 days, the rest 90. The counts on the Automation list never expire.

For agents: plain text of this guide · all guides

For agents

Guide: Runs: what each automation did

This page: https://commentwatchdog.com/help/keyword-automations/runs-what-each-automation-did

Topic: Automation

Time: about 3 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: For any comment or message, you can see what the automation did, step by step, with the exact messages.

Context: Every time an automation acts, a run is written: the person, the steps it took, the outcome. Runs are grouped by day, newest first, and the outcome is the one pill at the end of a row: Done, Waiting, Needs a person, Skipped or Failed. A run opens beside the list with its steps, their times and the messages as they were sent, and the chat one click away. A flow's run can also be followed step by step on the canvas; that is its own guide.

Before you start

1. Skipped runs are kept 30 days, the rest 90; the counts on the Automation list never expire.

2. Needs a person means someone on your team has to act: a draft to review, a chat handed over.

3. New runs land at the top on their own.

Steps

Step 1 of 5: Open Runs from an automation's menu.

Where: On the Automation list, the three dots at the end of a row, then See runs. The numbers beside an automation's name in its editor open the same page. Runs opens with a small tag naming that automation; its x shows every automation's runs.

Screenshot: https://commentwatchdog.com/media/shots/automation-home-menu.en.webp (See runs, in a row's menu.)

Screenshot: https://commentwatchdog.com/media/shots/automation-home-menu-phone.en.webp (See runs on a phone.)

You should see: Runs: everything the automations on the page did, newest first.

Step 2 of 5: Read a run's row.

Where: When it happened, the person with the automation's name under theirs, then What happened: the steps in order (Matched · Sent) ending in the outcome pill, here Done. Search people, above the list (or the key /), finds a person by username or name.

Screenshot: https://commentwatchdog.com/media/shots/automation-runs.en.webp (One run: when, who, which automation, and what happened.)

Screenshot: https://commentwatchdog.com/media/shots/automation-runs-phone.en.webp (A run's row on a phone.)

You should see: The runs in day groups, each group with its count, and one pill per run.

Step 3 of 5: Filter to the runs that need you.

Where: Needs a person, beside All above the list: the runs where someone on your team has to act. Skipped, next to it, lists the people an automation passed over, each with the reason.

Screenshot: https://commentwatchdog.com/media/shots/automation-runs.en.webp (Needs a person, with its count.)

Screenshot: https://commentwatchdog.com/media/shots/automation-runs-phone.en.webp (The same filter on a phone.)

You should see: Only those runs, with the count beside the filter.

Step 4 of 5: Open a run.

Where: Click a row. The run opens at the side: the person, the automation and the time at the top, the outcome under them, then each step with its exact time and the message as it was sent. The arrows at the top (or the keys J and K) move to the next and the previous run; Esc closes.

Screenshot: https://commentwatchdog.com/media/shots/automation-runs-drawer.en.webp (A run, opened: each step with its time and the message as sent.)

Screenshot: https://commentwatchdog.com/media/shots/automation-runs-drawer-phone.en.webp (A run on a phone.)

You should see: The message they wrote and the exact message that went back.

Step 5 of 5: Open the chat it belongs to.

Where: Open the thread, at the bottom of the run, opens that person's chat in Messages. Copy run id, beside it, copies the id to quote to support.

Screenshot: https://commentwatchdog.com/media/shots/automation-runs-drawer.en.webp (Open the thread, at the bottom of the run.)

Screenshot: https://commentwatchdog.com/media/shots/automation-runs-drawer-phone.en.webp (Open the thread on a phone.)

You should see: The chat in Messages, where each automated message carries the automation's name.

If something is off

Problem: A run says Waiting

Fix: On Instagram a private reply to someone who does not follow you lands in their Requests folder, and Instagram does not report whether it was seen; the run waits for their reply or tap.

Problem: A run says Failed

Fix: The row says why in words: The page's connection needs reconnecting, Meta refused it, The 24-hour window had closed. A Meta error carries its number.

Problem: A run says Skipped

Fix: The reason is on the row: reply window closed, already had it, outside business hours, daily cap reached, the automation was paused, they asked not to get automated messages.

Problem: A person is shown as Forgotten person

Fix: They were forgotten under People; their runs stay without a name.

Common questions

Question: Do new runs appear on their own?

Answer: Yes, the page checks every 20 seconds and lands new runs at the top with a soft highlight.

Question: Can I search runs by the person?

Answer: Yes, by the username or name; press / to jump to Search people.

Question: How long are runs kept?

Answer: Skipped runs are kept 30 days, the rest 90. The counts on the Automation list never expire.

Related guides

Follow a run step by step: https://commentwatchdog.com/help/flow-builder/follow-a-run-step-by-step

Retry failed runs: https://commentwatchdog.com/help/flow-builder/retry-failed-runs

The Automation list: https://commentwatchdog.com/help/keyword-automations/the-automation-list

Plain text of this guide: https://commentwatchdog.com/help/keyword-automations/runs-what-each-automation-did.md

All guides for assistants: https://commentwatchdog.com/help/llms.txt

Put a watchdog on your pages tonight

Meta API approved Start your free trial

Free for 7 days, no credit card required