# plan.run.StepOutcome.refusal

- **Module:** plan.run.StepOutcome
- **Package:** libtmux
- **Language:** Rust
- **Kind:** method
- **Source:** https://github.com/libtmux/libtmux-rs/blob/f0e37052c232636b61d095817046e6bfc8f2ca40/crates/libtmux/src/plan/run.rs#L208
- **Page:** https://libtmux.org/en/rs/latest/reference/plan-run-stepoutcome-refusal/

```
plan.run.StepOutcome.refusal(self) -> Option<Error>
```

Why tmux refused this invocation, in the crate's error vocabulary.

A refusal is data rather than an error here, because a plan may expect
one. Without sensitive input, this classifies it the same way a direct
call would, so a caller can match on [`Error::SessionExists`] rather
than racing another session creation. A sensitive invocation reports
[`Error::CommandFailed`] and withholds tmux output.

`None` when the invocation succeeded.