Mankomail

Stop ​

Ends this execution branch with a readable status and reason.

The Stop node ends the branch it sits on, with a status and a reason that show up in the run detail. It has no output: nothing can be connected after it.

A branch that simply has no next node also ends. Add a Stop node when you want the end to be explicit and traceable, typically on the "no" side of a Condition or on the otherwise branch of a Switch: "Ignored — auto-reply" is easier to read in the journal than a branch that silently stops.

At a glance ​

  • Type: flow.stop · version 1
  • Category: Logic
  • Kind: Step — one stage of a run
  • Effect: No external effect (none) — nothing is written outside Mankomail; safe to replay
  • Needs a carrier email: No
  • Connection: None
  • Inputs: main
  • Outputs: Computed from the parameters

Parameters ​

status ​

Status

  • Type: One choice (options)
  • Required: Yes
  • Default: success
  • Options:
    • success — Done: The expected work is done, the branch ends normally.
    • ignored — Ignored: This email is out of scope for this workflow — useful to trace what was skipped.

reason ​

Reason — Text shown in the execution journal. Accepts {{ }} expressions.

  • Type: Text (string)
  • Required: No
  • Default: "" (empty)
  • 500 characters at most
  • Example: Out of scope: auto-reply
  • Expressions: {{ }} accepted

Outputs ​

Computed from the parameters.

None — the branch ends here

Data produced ​

What this node adds to the run data, and how to read it in an expression. <step> stands for the step key: the node name turned into an identifier (see Data and expressions).

  • {{ data.<step>.status }} — string. success (Done) or ignored (Ignored), as set in the node.
  • {{ data.<step>.reason }} — string. The reason, rendered (expressions resolved) and trimmed. Empty when none was given.

Example ​

A support workflow should not answer automatic replies. After a Condition node on email.signals.isAutoReply equals true, connect the true port to a Stop node with:

status: ignored
reason: Out of scope: auto-reply from {{ email.from.email }}

The run detail then shows the step with status ignored and the rendered reason.

Tips ​

  • Only the branch carrying the node ends; other branches of the same run keep running.
  • The status is recorded in the step data; it does not turn the run into a failure. To make a run fail on purpose, rely on the error handling of the node that detects the problem instead.
  • The reason is visible in the run detail but never written to the application logs, so it may quote email content.