# Response

> The server sends no channel response and no channel response finish on the channel; it sends no response on the scope after it receives the stop, and it sends the response finish of the scope.

Canonical: https://provider.diverge.network/2.3.0/endpoints/volumes-watch/client/stop/response/
Specification revision: 2.3.0

The server sends no frame on the channel. The answer to the stop is
the response finish of the scope.

- **Nothing on the channel.** The server sends no channel response
  and no channel response finish on the channel. The channel is never
  finished on its own; the response finish of the scope states, as
  [Scopes](/2.3.0/frames/scopes/) provides, that no frame bearing the scope
  follows on any channel.
- **After the stop.** The server sends no response on the scope after
  it receives the stop. A response the server sent before it received
  the stop may reach the client after the client sent the stop. The
  server sends the response finish of the scope after it receives the
  stop.
- **The sequence.** Zero or more responses that the server sent
  before receiving the stop; the response finish; nothing after it.