# Read a Paper watchdog report without disabling its protection

Paper's watchdog detects when the server stops making timely progress. A watchdog warning is evidence of a stalled or unusually long tick, not a diagnosis by itself. Disabling the watchdog can leave a genuinely stuck process consuming resources indefinitely. Preserve the report and identify the blocked work before changing protection settings.

## Capture the complete event

Record the event time, Minecraft/Paper version, player count and what happened immediately beforehand. Download the relevant section of `logs/latest.log`, including lines before the first warning and the thread dump that follows it. A screenshot of only the final line usually omits the stack trace needed for investigation.

Check whether the process recovered, stopped itself or was killed externally. Paper can emit an early warning before a later termination threshold. Those are different outcomes. A panel displaying an offline state after the event does not prove that the watchdog was the component that ended the process. Preserve exit information and resource history where available.

## Read the report as a snapshot

Find the server's main thread in the dump and note repeated method or plugin names. A stack frame identifies where a thread was observed, not necessarily the sole cause of the delay. Disk access, chunk generation, a synchronous plugin operation or external calls can appear differently. Avoid declaring a plugin guilty just because its name appears somewhere in a large dump.

Compare several reports from the same incident. An unchanged stack can suggest blocking; changing stacks may reflect expensive progress. Keep that distinction as a hypothesis until you have supporting logs or a profiler capture. Redact player addresses and secrets before sharing the report publicly, but retain a complete private copy.

## Investigate safely

If the server responds again, collect a short profiler capture during the same reproducible workload. Record recent plugin changes, scheduled backups and disk pressure. Test a suspected plugin change on an isolated copy or in a planned maintenance window. Do not unload random plugins or repeatedly force-stop a live world while players are building.

Check the documentation for the installed release. `max-tick-time` in `server.properties`, inherited Spigot timeout settings and Paper's early-warning options are related but use different locations and units. A setting described in current 26.x documentation may not match an older 1.21.11 layout. Do not paste a large timeout value merely because another server used it.

## Recover service and retain evidence

If the process is still unresponsive, send the log and current panel state to support. A clean stop is preferable when the console can process it. If a forced stop becomes necessary, make that a deliberate recovery decision with awareness of unsaved progress, rather than a repetitive troubleshooting step.

Roll back a known recent configuration or plugin change only after preserving evidence and checking compatibility. Keep the watchdog enabled while you verify normal operation. Success means the triggering workload completes without new stalls and the underlying cause has been addressed; a quiet console after suppressing warnings is not sufficient.

## Related help

- [Find Minecraft logs and send useful troubleshooting details](https://help.cloudexa-hosting.com/books/game-hosting/page/find-minecraft-logs-and-send-useful-troubleshooting-details)
- [Diagnose Minecraft lag with TPS, MSPT and spark](https://help.cloudexa-hosting.com/books/game-hosting/page/diagnose-minecraft-lag-with-tps-mspt-and-spark)
- [Tell a Java memory error from a killed Minecraft process](https://help.cloudexa-hosting.com/books/game-hosting/page/tell-a-java-memory-error-from-a-killed-minecraft-process)

## Reference

[Paper basic troubleshooting and watchdog reports](https://docs.papermc.io/paper/basic-troubleshooting/). [Server watchdog property](https://docs.papermc.io/paper/reference/server-properties/). [Paper early-warning configuration](https://docs.papermc.io/paper/reference/global-configuration/).