Applies to

DocuWare on-premises. 7.0–7.6 only.

What to check

A full-text reset adds extraction and indexing work to the database. Several resets running together can overwhelm a slower system and delay unrelated background work such as Autoindex.

Practical steps

  • Check whether multiple cabinets are being rebuilt and monitor database, CPU and memory pressure.
  • Schedule one cabinet's reset at a time and use the appropriate retry scope for failed or unprocessed documents.
  • Have a DocuWare administrator assess stalled task queues using the source's version-specific recovery guidance and a verified backup.

Confirm the result

Confirm that the queue drains and other jobs recover before starting another reset. Do not apply the legacy Tomcat memory settings or database cleanup instructions to a newer search architecture.