Home
/
Glossary
/
Scenario execution

Scenario execution

Definition

A scenario execution, or automation execution, is one run of one Inrō scenario for one contact. Each contact who triggers it gets their own run, always in one of six states, from Pending to Completed.

A scenario execution is one run of one Inrō automation for one contact. Every contact who triggers a scenario gets their own execution, and it is always in one of six states: Pending, Completed, Failed, Interrupted, Limit reached or Disconnected. When an automation "did nothing", the state of the execution tells you why.

What counts as one automation execution?

One contact going through one scenario, once. If two people comment on a post that fires a comment-to-DM automation, you get two executions. Each moves through the flow on its own.

Duplicate protection stops a scenario from starting a second run for a contact who already has a run of it in progress. A DM campaign creates executions too, one per contact, with the same six states.

What are the six execution states in the app?

  • Pending: the run has started and is not finished. Cause: a step is running, a delay is counting down, or a step is waiting for a reply or a click.
  • Completed: the run reached the end. Cause: every step on the contact's path ran and there is no next step.
  • Failed: the run stopped on an error. Cause: a step hit an error it could not recover from.
  • Interrupted: the run was stopped before the end. Cause: you cancelled it, or the contact entered an excluded folder or matched an exclusion rule.
  • Limit reached: the run is held before its first step. Cause: your account reached its monthly contact activation limit.
  • Disconnected: the run is held before its first step. Cause: your Instagram connection is broken.

Why a folder stops a run is covered under mid-flow interruption.

While a run that messages the contact is Pending, the AI agent holds back in that conversation until the run ends.

What do Limit reached and Disconnected mean?

Both hold the run before it sends anything, instead of dropping it. Limit reached comes from your plan's cap on contact activations, Disconnected from a broken Instagram connection.

One case ends a held run for good: if it started from a comment and that comment is now more than 7 days old, it ends as Interrupted. Meta only allows a private reply to a comment within 7 days of it (Meta for Developers, private replies, checked September 2026).

Where do you see your executions?

On the scenario's History tab. Each row is one execution, with the contact, a timestamp and the status, and you can filter by any of the six states. You can retry a Failed or Interrupted run from the step that stopped, and it goes back to Pending. For the wider picture, see the guide to Instagram DM automation, or browse the other terms in the automation glossary.

Try Inrō and leverage the power of Instagram marketing automation

Attract more leads, target them with DM marketing, and automate all your interactions on Instagram!

Free plan available
Meta Tech Provider
Setup in 5 minutes