Starting with Resilio Connect 2.9 and above, it is now possible to ignore error messages.
This is purely UI functionality - ignored errors are simply not reported in MC even though they're still valid for an Agent and might prevent jobs from completing! Do not ignore the error message that you're not sure about and that might be critical for you to identify that the job run has stuck. Mail notification is not sent for the ignored errors as well.
It can be done from the error message itself by clicking to ignore an error (only one error message can be selected at a time.)...
...or from MC Settings -> Manage Errors.
Starting with v3.5.0 the behavior is reverted and Resilio Admin needs to choose the Agents and Jobs for which the error will be ignored.
The exceptions in 3.4.x and older work the following way:
Note, it's the error message itself that is ignored. It means that if several agents have the same error message, it's sufficient to select it for at least one agent and click "Ignore the error", and it will be ignored for all other agents in all other jobs. In the example above for the exception list of AgentA and AgentB, and Job1:
- Agents A and B will show error (= not ignore) for all their jobs;
- All agents in Job1 will show error (=not ignore)
The inclusions in 3.5.0 work the following way:
- selected Agent will ignore (=not show) the error for all their jobs;
- all agents in selected jobs will ignore (=not show) the error.
The error message will be ignored for the job, all its currently active runs and next runs. If this error appears on an already competed (failed / aborted) job run the error will remain there. That also means that if the error is "un-ignored", it won't re-appear on finished job runs. It's so because a finished job run is a kind of a snapshot and cannot be changed at all.
The errors are listed by error codes. Refer to the table here for the most popular error codes. If you encounter some error messages that you need help with, please contact support.
It's highly not advisable to ignore error code "SE_OPERATION_ABORTED".