| Previous | Next |
| FSRM_E_FILE_MANAGEMENT_JOB_NOT_LEGACY_ACCESSIBLE | FSRM_E_CANNOT_USE_DEPRECATED_PROPERTY |
FSRM_E_FILE_MANAGEMENT_JOB_MAX_FILE_CONDITIONS
FSRM_E_FILE_MANAGEMENT_JOB_MAX_FILE_CONDITIONS means another selection condition cannot be added to the file-management job. FSRM jobs can filter by location, classification properties, and file timestamps, but the object enforces a finite condition set.
Simplify the selection policy
- Enumerate existing conditions and remove duplicates or conditions made obsolete by classification.
- Move complex logic into a classification property and let the job test the resulting value.
- Split independent policies into separate jobs with nonoverlapping scopes and actions.
Adding more conditions is not always equivalent to better precision. Several timestamp and property clauses can make a policy difficult to audit and may interact differently in continuous jobs. Consolidate reusable logic in classification rules, document whether conditions are combined as intended, and verify the effective file set with reports before enabling destructive actions.
File management tasks · File management job · Classification management
Looking for a different code? Search another status or error code.