Pause Queue
Published 17 Sept 2026
Stops TipLink processing events, and starts it again. The panic button: everything goes quiet without you disconnecting a single platform or disabling a single alert.
Events still arrive and are still recorded while paused. They are held, not thrown away.
Settings
| Setting | What it does | Default |
|---|---|---|
| On press | Toggle pause, Pause only or Resume only. | Toggle pause |
| Label | A word of your own in place of the state word. Leave blank for Running / Queue held. | Blank |
| Show waiting | On adds a count of how many events are being held. | On |
On the Key
| What it shows | When |
|---|---|
A green play triangle over Running | Events are being processed normally. |
Amber pause bars over Queue held | Paused. |
A third line, 12 waiting | Events are being held. It only appears when there are some, so a clear queue does not carry a permanent 0 waiting. |
Queue … | Connected, but TipLink has not reported the queue state yet. |
Offline | TipLink is not running. |
The held count is the reason to look at this key rather than just press it.
What Pausing Actually Does
| Paused | Not paused | |
|---|---|---|
| Events arrive from platforms | Yes | Yes |
| Events are recorded in Activity | Yes | Yes |
| Alerts fire and actions run | No | Yes |
| Actions already running | Finish normally | - |
So a pause is a hold, not a mute. Resume and the held events run through in order.
Nothing is dropped while paused. If you hold a busy stream for ten minutes and then resume, every one of those events fires. Watch the count on the key before you press resume, and consider disabling the noisy alert sets instead if the pause is going to be a long one.
Pause, Resume or Toggle
Toggle is right for a single panic key you press twice.
If you want a deliberate pair - one key to stop, one to start - use Pause only and Resume only. A Pause only key cannot accidentally restart a stream's worth of held events, which is the mistake worth designing out.
Common Uses
The panic key
One key, Toggle, somewhere you can hit it without looking. Something goes wrong, you press it, everything stops reacting while you sort it out.
A break key
Pause before you step away, resume when you come back. Nothing is lost, and your viewers' tips still land in your stats and on the Activity page.
An interview or a guest
Pause for the segment. Everything is recorded, nothing fires on screen, and you can resume once you are back to normal programming.
Things to Watch For
This is the same switch the app has. Pausing here is exactly the app's own pause, so the key follows if you pause from the TipLink window instead, and a pause survives closing the app.
It does not stop the platforms. Chat is still being read and tips are still being recorded. Use Platform Connection if you want a platform genuinely disconnected.
Device limits still apply on resume. PiShock and OpenShock intensity limits are applied when the held events run, not when they arrived, so a backlog cannot exceed them.
Related
- Activity - what was recorded while you were paused.
- Toggle Alert - silence one alert or set rather than everything.
- Platform Connection - stop events arriving at all.