| Previous | Next |
| FSRM_E_PROPERTY_MUST_APPLY_TO_FILES | FSRM_E_CLASSIFICATION_PARTIAL_BATCH |
FSRM_E_CLASSIFICATION_TIMEOUT
FSRM_E_CLASSIFICATION_TIMEOUT means an FSRM classification request did not finish within the configured or internal time budget. Unlike a module timeout, this result describes the classification operation as a whole and can involve scope size, storage latency, or several modules.
Locate the slow stage before increasing limits
- Use the report and event log to identify the last volume, file, rule, or module processed.
- Test the same rules against a small local scope to separate configuration failures from scale.
- Check remote storage, content readers, antivirus filters, and module-host resource pressure.
Simply rerunning a large scan can reproduce the timeout and create another partial result. Reduce scope or rule count for diagnosis, then measure which component consumes the time. If a third-party classifier is responsible, use its own logging and supported timeout controls. Preserve completed property values unless the policy requires an all-or-nothing decision.
Classification manager · Classification management · Pipeline module implementation
Looking for a different code? Search another status or error code.