| Previous | Next |
| FSRM_E_CLASSIFICATION_ALREADY_RUNNING | FSRM_E_FILE_MANAGEMENT_JOB_ALREADY_RUNNING |
FSRM_E_CLASSIFICATION_NOT_RUNNING
FSRM_E_CLASSIFICATION_NOT_RUNNING means a caller attempted to cancel, wait on, or otherwise control classification when the service had no queued or active classification operation corresponding to that request.
Reconcile client state with FSRM state
- Read the current running status before issuing cancellation or completion-control calls.
- Do not assume a process-local flag proves that the service still owns the same run.
- Check the last report and last error to determine whether the run completed between calls.
This can be a benign race: classification may finish after the client checks status but before it sends cancel. Treat that case as completion, not as a reason to launch another run immediately. If automation repeatedly loses track of jobs, centralize ownership and persist the start time, context, and final result instead of inferring state only from the caller process.
Classification manager · Running status · RunClassification
Looking for a different code? Search another status or error code.