# types.TmuxPaneFlowEvent

- **Module:** types
- **Package:** libtmux
- **Language:** TypeScript
- **Kind:** interface
- **Source:** https://github.com/libtmux/libtmux-ts/blob/46cccfef2a546de55ce8b308249b8c76339089a0/packages/libtmux/src/types.ts#L813
- **Page:** https://libtmux.org/en/ts/latest/reference/types-tmuxpaneflowevent/

tmux paused or resumed output for a pane that fell behind.

This connection answers every `pause` it observes with its own
[`refresh-client -A <pane>:continue`](/en/tmux/latest/manual/refresh-client/) (see [`WatchOptions.pauseAfterSeconds`](/en/ts/latest/reference/types-watchoptions-pauseafterseconds/)),
whether tmux paused the pane on its own or a caller paused it directly with
`server.cmd("refresh-client", ["-A", "<pane>:pause"])` on this same
connection's client. A pause held that way is resumed within one round
trip; it does not stay paused for the caller to inspect.

`pause`/`continue` and `off`/`on` ([`refresh-client -A <pane>:off`](/en/tmux/latest/manual/refresh-client/) / `:on`)
are independent pairs tmux tracks separately. Resuming with the wrong verb
- `off` then `continue`, or `pause` then `on` - returns success but leaves
the pane's output undelivered; `off` stops tmux from reading that pane's
pty at all, which also freezes it for every other client, not only this
connection's.

## Members

### Other members

- [`kind`](/en/ts/latest/reference/types-tmuxpaneflowevent-kind/) (property)
- [`paneId`](/en/ts/latest/reference/types-tmuxpaneflowevent-paneid/) (property)