# After a crash or force quit

- **MCP resource:** rdmbench://help/interrupted
- **Version:** 0.12.0
- **Runs on:** macOS 15 Sequoia or later, Apple silicon or Intel
- **Needs:** An Enttec DMX USB Pro with its DMX/RDM firmware (major version 2), or, on a rig, an Art-Net 4 node with RDM on at its ports
- **Price:** Free

If RDMBench is force quit, crashes, or loses power while it is
monitoring a fixture, walking its channels, testing it under load,
sweeping its modes or holding DMX, the next launch says so. The same goes for the command line
and for an assistant's server on this computer: whichever of them opens
next sees what the others left.

## What the launch shows

An **Interrupted Work** sheet *(macOS)* / dialog *(Windows, Linux)* lists each thing that was running, with the
fixture, the line it was on, when it started, and what ran it. Each row
has its own choices, and each one takes effect as soon as you click it.
The highlighted button is the usual choice.

- **Monitoring.** **Close with Summary** writes the session's summary
  from the readings it had already saved. Nothing is estimated: the
  summary is the one it would have had, up to its last reading. It is
  marked as ended by a crash, never as a normal stop. **Keep As It Is**
  leaves the readings with no summary. **Discard…** deletes the
  session; click it a second time to confirm.
- **Channel walk.** Every mark is saved as it is made, so nothing you
  marked is lost. **Resume** opens the walk again with your marks, at the
  first channel you hadn't marked. It needs the fixture on the line, so
  it waits until RDMBench has connected and found it. **File as
  Incomplete** files the walk as it stood. The repair sheet says it was
  not finished. **Discard…** deletes it.
- **Load test.** A load files its result only once output is down, so
  one cut off has nothing to recover. The sheet *(macOS)* / dialog *(Windows, Linux)* says it was
  interrupted.
- **Mode sweep.** The row says which mode the sweep left the unit in,
  and the mode and address it came from. **Put Back** sets the unit
  back once its line is open and the unit is on it, then takes its
  report again. **Leave It** takes the row off the list and leaves the
  unit as it is. See [Fine in one mode, not in others](/help/mode-sweep/).

**Done** closes the sheet *(macOS)* / dialog *(Windows, Linux)*. A monitoring session, walk or mode sweep you
haven't dealt with stays on the list. **File → Interrupted Work…** *(macOS)* / **File → Interrupted work…** *(Windows, Linux)* opens the
sheet *(macOS)* / dialog *(Windows, Linux)* again, for example once the fixture is plugged in, and the next
launch asks again.

## If DMX was being held

The widget keeps sending its last levels after RDMBench is gone. It
stops at the next RDM message on that line, and nothing else stops it.
So the fixture may still be lit, or still at full if a load test was
running, until something talks to it.

When RDMBench opens, it connects to the widget if it is the only one
plugged in, then discovers, and that ends the output. The row then says
**Output ended when the line was reopened**. RDMBench never asks about
this, because there is only one right answer.

If the row says the line **has not been reopened**, the fixture may
still be lit. Connect to that widget, or unplug it.

Through an Art-Net node it is different. A node keeps sending its last
levels for as long as RDMBench is gone, however long that is. So when
RDMBench opens, it sends that universe every channel at zero straight
away, and the row says so. If the node does not answer, or something
else is sending to the universe now, nothing is sent and the row says
why. Then check the fixture, and if it is still lit, power-cycle the
node.

## From the command line

`rdmbench-cli recover` lists what every run on this computer left,
numbered, with what can be done about each. Each item also says when a
held output's line still needs to be reopened.

`rdmbench-cli recover 1 close` does one of those things to item 1. The
choices are `close`, `keep` or `discard` for a monitoring session, and
`resume`, `file` or `discard` for a channel walk. `resume` carries on
with the walk at the keyboard. `restore` puts back a unit a mode sweep
left in another mode, and needs its line. A load or held output has
only `dismiss`, which takes it off the list, and a sweep has it too. Add `--json` to the list for a
script. Any command that talks to a widget's line, `rdmbench-cli
discover` for one, also ends output a crashed run left on it. Output
held through an Art-Net node has `end` as well, which sends the node
every channel at zero; nothing else ends it.
