Analysis does not finish
Open Settings → Background processing (Einstellungen → Hintergrundverarbeitung). Check Action Scheduler availability, queued/failed jobs and the displayed cron status. If WordPress cron is disabled, the host must provide a working server cron or external runner. Fix that runner rather than repeatedly starting the same analysis.
On resource-limited hosting, use the automatic processing adjustment or reduce the configured batch size. After fixing the cause, refresh the analysis and wait for a completed result. Avoid running overlapping manual changes to the media library while diagnosing.
Expected duplicates are missing
The tool detects exact file duplicates, not visual similarity. Differently encoded or resized images may not be duplicates. Check whether indexing finished and whether the result is current.
Cleanup is blocked
Read the item’s reason. Common causes include unsupported references, changed files, disabled recovery, insufficient disk space or an unsuccessful recovery-protection check. Leave blocked items intact. Refresh the analysis after correcting the cause and use another test run before execution.
Recovery protection fails
Ask the host to verify that the uploads recovery directory cannot be downloaded publicly and that the server can reach its own uploads probe. Nginx and proxy setups must enforce the required denial; creating an Apache protection file alone is insufficient there. See Recovery.
A restore fails or disk usage has not dropped
Review file/attachment conflicts and whether the recovery copy still exists. Later content edits may prevent a safe automatic restore. Disk usage can remain high while temporary recovery copies exist; review retention and expired-copy processing before deleting any copy you may still need.
A Pro report is missing
Confirm Pro is installed, reporting is enabled, a baseline exists and a completed later run changed the tracked counts. Then check the recipient and mail delivery. An unchanged run does not require a report.
Contact support
Provide the version and edition, run status, item-level error and a redacted screenshot through IPS support. Include the web-server type for protection problems. Do not send recovery archives or private media unless specifically needed and shared through an appropriate private channel.