[Bug]: User username still has unscanned files after running background scan, background scan might be stopped prematurely

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

Hi! I am constantly getting warning message for one of users (out of 25):
User username still has unscanned files after running background scan, background scan might be stopped prematurely
And this happens once per an hour.

Steps to reproduce

1. Just observ in logs the warning message User username still has unscanned files after running background scan, background scan might be stopped prematurely

Expected behavior

No warning message or more explanation added.

Installation method

Community Web installer on a VPS or web space

Nextcloud Server version

27

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.2

Web server

Apache (supported)

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

Start by locating the warning text in the Nextcloud Server code and trace the background scan path that emits it. Reproduce the hourly warning with the reported Nextcloud 27, PHP 8.2, Apache, and MariaDB setup while collecting logs; done means the scan completes reliably or the warning explains the actionable cause. The issue provides no named files or tests.