Shock Delivery & Queues
Shock requests can come from device controls, a keyholder, chat, games, a coach, or scheduled actions. Depending on your settings and connection, a request can run immediately, wait in a queue, or fail. A successful request does not necessarily mean the device has finished executing it.
This guide covers delivery and queue controls. For pairing, supported models, consent, and strength settings, start with Supported Devices.
Find the controls
- Open Device Shock Settings and find Queue undelivered shocks to review the queue's behavior, limits, and pauses.
- Open Recent shocks from the dashboard to inspect Delivery tracking, connection reports, and individual results.
- Use the queue's Pause queue, Resume queue, and Retry now controls when available. Device stop controls serve a different purpose.
Availability depends on the selected device, installed app, and features enabled for your account. Use the settings and session status actually shown; an account preference alone may not describe an existing session's saved policy.
Already accepted tracked deliveries keep their recorded delivery policy and pause between deliveries. Changing the preference does not rewrite those existing entries.
Choose a Bluetooth queue mode
| Mode | What happens to undelivered requests | Connection needed | Normal timer unlock |
|---|---|---|---|
| Retry for a limited time | Requests can wait until their expiry. This mode does not track full Bluetooth execution. | Compatible Web Bluetooth browser, or the Android/iOS app. | Does not add a queue-based unlock requirement. |
| Deliver every queued shock | Accepted requests have no ordinary queue expiry and can remain after the lock ends. | A compatible, updated Android/iOS app reporting completion. | Does not add a queue-based unlock requirement. |
| Deliver before timer unlock | Retains accepted requests and requires matching mandatory deliveries to complete or be resolved. | A compatible, updated Android/iOS app reporting completion. | Can postpone normal unlock of an eligible timer session. Card-based locks are not affected. |
To select an app-only mode, open the settings in the native app with its command service connected. A mobile browser or Home Screen website shortcut is not the native app. If a mode is unavailable, check the message about app support and service readiness.
For native Bluetooth delivery, two connections matter: phone ↔ server and phone ↔ device. Bluetooth can be connected while the phone's command service is offline. On Android, check Native service and Remote commands. On iPhone, open Chastify in the foreground and check the device connection. You can use the website elsewhere while the phone handles eligible delivery.
For time-limited browser delivery, keep the Chastify page open and connected to the device. A connected browser cannot complete an app-only queue.
The queue-based unlock requirement applies to normal timer unlock. It does not add a new blocker to an otherwise available emergency release, authorized keyholder release, or maximum-time safety ending.
Cellmate Pro 3 / Cagink Pro 3 over 4G
When a supported Pro 3 is configured for 4G and queueing is enabled, delivery is handled through Qiui's network. It does not require the phone's Bluetooth connection or an open phone app. The device still needs power, its 4G mode enabled, and mobile coverage.
Check Recent shocks for the server's 4G attempts, last device reply, and next eligible retry. A previous reply does not prove the device is online now. Completion is based on device replies received by the server, rather than a native Bluetooth completion report.
4G queued shocks do not block normal timer unlock. Waiting 4G work can allow Bluetooth deliveries to proceed, so do not assume every transport shares one uninterrupted queue order. A missing 4G reply cannot be repaired by reconnecting Bluetooth alone.
Limits, spacing, and locked settings
The available settings include:
- Expire queued shocks after: a choice from 5 minutes to 24 hours in time-limited mode. This expiry does not apply to the two no-expiry modes.
- Maximum queued shocks: a limit from 1 to 100, or Unlimited. The Unlimited option still has a 1,000-event safety cap. A full queue can reject a new request.
- Pause between queued shocks: choose no added pause or a supported interval up to 5 minutes. Connection, permissions, and other pauses can delay the next delivery further.
- When stopping a manual shock on the lock control page: choose the supported stop behavior described below.
During an active lock, Lock queue settings for this session asks you to confirm the current queueing, mode, expiry, capacity, spacing, and stop behavior. After confirmation, those settings cannot be changed through ordinary settings until that session ends. Starting a later session does not automatically lock its settings.
Hardcore Mode can separately prevent weakening an active strict delivery policy. Configure and review the policy before confirming either restriction. Locking queue settings does not remove the Stop All, queue-pause, hygiene, or authorized safety controls.
Turning off queueing is not a way to erase all previously accepted work. Completion-tracked deliveries can remain pending. Some game effects are also scheduled to follow their animation even when ordinary offline queueing is off.
Read delivery status
Recent shocks separates unfinished tracked deliveries from completed or resolved results and ordinary request receipts. Check the event's source, device, timestamps, and confirmed progress.
| Status or result | Meaning |
|---|---|
| Accepted / Queued | The request was accepted or saved for delivery. It may not have reached the device. |
| Received by app / Started | The app acknowledged a delivery stage. Full execution has not yet been confirmed. |
| Full execution confirmed | Chastify accepted the native app's completion report. |
| All 4G commands acknowledged | The server received the required 4G command replies. |
| Waiting to retry / Paused by safety stop | Work remains, but another eligible attempt is not currently running. |
| Skipped for now / Completion unconfirmed | Execution is unresolved. Follow that entry's recovery instructions rather than sending the same request again. |
| Cancelled / Rejected / Authorization revoked | The request was resolved without being counted as fully completed. Read its reason. |
Confirmed progress is the last accepted report, not a live countdown or proof of physical sensation. A command timer reaching zero is not a completion receipt. Likewise, no pending-shock unlock blocker does not mean every delivery completed or that all other unlock requirements are satisfied.
If refreshing diagnostics fails, any retained information is from the last successful check. Missing diagnostics do not establish that the queue is empty.
Stop, pause, and retry
| Control | What it does |
|---|---|
| Pause queue | Holds upcoming queued deliveries until you choose Resume queue. Output already being sent or running may continue. Time-limited requests can still expire. |
| Resume queue | Removes your manual pause. Connection checks, queue order, hygiene, spacing, and safety restrictions still apply. |
| Retry now | Requests another check of eligible queued work. It does not bypass earlier entries, safety checks, or missing completion evidence. |
| Stop All Shocks | Requests that output stop and applies the safety-stop behavior. It is not a promise that every persistent delivery is permanently cancelled. |
Closing the app, turning off Bluetooth, or ending the lock does not reliably stop output already accepted by the device or remove persistent queued work. Use the appropriate stop control, check the physical device, and inspect Recent shocks before reconnecting or sending more requests. Pause queue can hold future work while you investigate; it does not stop current output.
Manual stop behavior
For a shock started manually by the wearer or keyholder on the lock control page, the setting offers:
- Safety pause: requests a stop and briefly pauses delivery. The requester's cancelled work can be removed, while other interrupted persistent deliveries can remain unfinished.
- Cancel this shock and continue the queue: cancels that active manual shock's remaining duration and its associated unlock requirement. This requires a running, completion-tracked Lockink shock and an updated Android/iOS app. The next eligible request can proceed after the app confirms a safe stop, without the extra safety-stop pause.
The faster continuation option does not change chat, game, bot, scheduled, or other automatic shock stops. Timed Random/Berserk modes, unsupported devices, older apps, and Web Bluetooth use the safety-pause path. Separate Stop All controls remain safety stops. Read the resulting status rather than assuming that pressing Stop erased the entire queue.
Hygiene openings
While a Hygienic Unlock is active, pending queued deliveries wait for confirmed relock. The hygiene countdown expiring or Bluetooth reconnecting does not end that pause. Ending or abandoning the associated lock removes its hygiene hold, so do not rely on that hold to pause persistent deliveries after the session ends. Time-limited requests retain their original expiry; persistent requests remain saved.
This queue pause does not stop output already in progress. After relock, the queue still follows any manual pause, safety stop, spacing, connection, and permission checks.
Interrupted deliveries
If execution is interrupted, open Chastify on the phone that was delivering it and follow the entry's instructions. The app can report what happened after reconnecting. Only a confirmed safe retry point allows the recorded remaining duration to be retried; reconnecting is not permission to replay an uncertain command blindly.
During recovery, an unconfirmed delivery can be set aside so later eligible work can continue. In no-expiry modes, it can remain saved without blocking normal timer unlock. Time-limited recovery can instead end in cancellation. These outcomes are not completion, and they do not occur on a guaranteed screen countdown. Read the individual delivery's current result and unlock status.
For a 4G command with an uncertain result, follow its 4G recovery status. Do not assume the server will repeat an unacknowledged command or that reconnecting the phone will resolve it.
After a session or device change
In the two no-expiry modes, accepted eligible requests can survive timer expiry, keyholder unlock, emergency release, abandonment, and starting another lock. They keep their original session identity. Old shocks do not become mandatory unlock requirements for a new session. Current consent, relevant permissions, explicit cancellations, and device safety checks still apply.
Changing the selected device does not transfer an old request to the replacement device. An entry can show Saved for … — device not selected. Select and connect the original device if you intend to resume that delivery. Other work for the currently selected device may proceed.
Changing chat-shock permissions
When disabling new chat shocks or tightening applicable chat limits, Chastify may show affected queued requests and ask whether to Keep existing shocks or Remove existing shocks. Keeping them preserves their existing authorization subject to other checks; removing them cancels the affected requests. This choice does not remove unrelated work from other sources.
Review that confirmation separately from the account's general queue switch. Do not assume that disabling new requests automatically removes every accepted request.
Troubleshooting
- Open Recent shocks and refresh. Check whether the request is pending, running, completed, cancelled, or awaiting recovery before sending another.
- Confirm the target device and transport. For native Bluetooth, check both the command-service and Bluetooth reports. For 4G, inspect device replies and wake-up attempts.
- Check manual queue pause, hygiene/relock status, safety stop, spacing, expiry, and permissions.
- If Retry now is available, use it to check the existing request. A retry request is not itself confirmation of delivery.
- If a required delivery still blocks normal timer unlock, inspect that entry's recovery status and the session's saved policy. Follow the existing unlock and safety-release options when applicable.
- For an unexplained failure, open Delivery help → Copy support details, review the text, and include it when contacting Support. Say what physically happened and when. Copying the details does not send a message automatically.
For pairing, permissions, or a connection that repeatedly drops, use Device Connection Troubleshooting.