| Previous | Next |
| FSRM_E_FILE_MANAGEMENT_ACTION_TIMEOUT | FSRM_E_MODULE_INVALID_PARAM |
FSRM_E_FILE_MANAGEMENT_ACTION_GET_EXITCODE_FAILED
FSRM_E_FILE_MANAGEMENT_ACTION_GET_EXITCODE_FAILED occurs after a custom file-management command has apparently completed, when FSRM cannot retrieve the process exit status needed to classify the action result. The file operation may already have taken effect.
Do not rerun the command blindly
- Check the action and FSRM logs for evidence that the target was changed successfully.
- Verify that the launched executable remains the process tracked by FSRM and does not immediately detach all work to an untracked helper.
- Avoid wrappers that close or replace process handles in unsupported ways.
Because the side effect can be complete even though the status is unknown, retries must be idempotent. Have the command write a durable result keyed by the target file, and return a normal exit code from the process FSRM launches. If a script starts asynchronous work and exits, redesign it so the tracked process waits and reports the final result.
Action command · File management tasks · File management job
Looking for a different code? Search another status or error code.