Fulltextsearch will not recognize/index files which were added via Shell and ./occ files:scan

Hi,

I have an issue with fulltextsearch but don´t know if this is possible or not.
I have read a lot of issues and was trying to find a solution with different searches in google but I could not bring it to work.

I want to add some files via the shell to my nextcloud folder and want that fulltextsearch is recognizing these files and index them.
But if I start ./occ fulltextsearch:live
my new files were not recognized and not indexed by fulltextsearch.

In general I try to copy a file for example "neu 1@2020-01-10_110217" to "new 1@2020-01-10_110217.txt" in a new folder and use after that the ./occ files:scan --path=/user/files/Zuhause so that Nextcloud is able to recognize it.

In the Nextcloud GUI, I can see the file after that action, but fulltextsearch is not recognizing it.
It seems there is some kind of notification missing in this process which will trigger fulltextsearch about that change in the filesystem.
If I run an ./occ fulltextsearch:index, I can search for the text inside the file.

I now wanted to ask, is there a way to achieve my goal of adding files to the filesystem and index them (somehow) with fulltextsearch?
(the original issue is that I wanted to sync my Backup Files from Notepad++ to Nextcloud and want to make them searchable, so that I have them with me all the time. Therefore I use the Nextcloud sync on the Backup folder of Notepad++ to have my files in Nextcloud. But all of these files have no extension, they have a format "neu 1@2020-01-10_110217" and I thought about to use now a script and the Workflow App in Nextcloud to copy my Backup Notepad++ Files to a new Folder and add the extension .txt to each of these files.
I was hoping that Full Text Search will index the files after I have added them with ./occ files:scan -path=/user/files/Zuhause but it doesn´t)

If I create a file with the Text App in Nextcloud, the fulltextsearch:live index is recognizing that and will index this file.
So I think the files app in Nextcloud will "tell" fulltextsearch somehow about the new created or modified file and Full text search is aware of it and will run the index.

In general I use the latest version 24.0.0 of Full text search, Full text search - Elasticsearch Platform, Full text search - Files and Full text search - Tesseract OCR.

I use Elasticsearch in Docker with version 7.12.0 with ingest-attachment.

I hope somebody from you can help me further.

Regards,
Joe

Start by reproducing the reported flow with ./occ files:scan --path=/user/files/Zuhause and ./occ fulltextsearch:live, then compare it with creating a file in the Nextcloud GUI. Trace whether the scan emits an event consumed by Full Text Search, using the reported Elasticsearch 7.12.0 setup. Done means either files added by the scan are indexed by live indexing or the limitation and supported workflow are documented.