Investigate a growing CoreProtect consumer queue without discarding it

Applies to: CoreProtect; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

A growing write queue can explain why recent actions do not appear in lookups yet. Preserve queued evidence and inspect database performance before pausing processing or restarting the server.

Follow the procedure

Capture /co status and the relevant startup or database error messages. Record the time so you can compare queue behaviour against the server’s player count and workload.
Check disk space and database availability through the panel or database administrator. A connection failure, full disk and slow storage require different corrections.
Repeat the supported status observation after a short interval. Determine whether the queue is shrinking, stable or growing rather than relying on one large number.
Read the /co consumer documentation before touching it. It is a console control that pauses or resumes processing; running it blindly can worsen an existing backlog.
Reduce avoidable high-volume work such as a planned mass edit while investigating. Keep ordinary logging enabled and ask support to assess persistent database errors.
After the underlying issue is corrected, observe the queue draining and query a known recent disposable block action. Record how long it takes to become searchable.

Check the result

The backlog should trend downward and newly recorded test actions should become visible after processing catches up. An enabled plugin with delayed lookups is not the same as lost evidence. Confirm both storage health and the recent test record before declaring recovery complete.

If the result is wrong

If processing remains stalled, preserve logs and request database-specific support before restarting or changing backends. Do not delete database files, discard queued records or repeatedly toggle the consumer. Restore a paused consumer only through the documented control once you know its current state.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report