# `BB.Error.State.ActuatorNotRunning`
[🔗](https://github.com/beam-bots/bb/blob/main/lib/bb/error/state/actuator_not_running.ex#L5)

A command could not be delivered because its actuator is not running.

The actuator is declared but has no process: its driver's `init/1` returned
`:ignore`, it is between crashing and being restarted, or the robot's
supervision tree is not up yet. Nothing received the command and nothing
will act on it.

`delivery: :pubsub` checks for the actuator before publishing, so in the
usual case the command never appears on the actuator's topic either. An
actuator that dies between that check and the call is reported the same
way, by which point the command has been published.

# `t`

```elixir
@type t() :: %BB.Error.State.ActuatorNotRunning{
  __exception__: term(),
  actuator: atom(),
  bread_crumbs: term(),
  class: term(),
  command: module(),
  path: term(),
  robot: module() | nil,
  splode: term(),
  stacktrace: term(),
  vars: term()
}
```

# `exception`

```elixir
@spec exception(opts :: Keyword.t()) :: %BB.Error.State.ActuatorNotRunning{
  __exception__: term(),
  actuator: term(),
  bread_crumbs: term(),
  class: term(),
  command: term(),
  path: term(),
  robot: term(),
  splode: term(),
  stacktrace: term(),
  vars: term()
}
```

Create an `Elixir.BB.Error.State.ActuatorNotRunning` without raising it.

## Keys

- :robot
- :actuator
- :command

---

*Consult [api-reference.md](api-reference.md) for complete listing*
