Statuses

error

the Agent encountered an error. See here for most frequent possible errors and suggestions to resolve them.

loading

the Agent was restarted - either the process itself, or simply the agent in the job run, and now it's reading and loading its database into memory. The more files are in the database, the longer it takes. Speed of loading depends on the speed of reading from disk.

waiting for files from source

valid for destination agents in Consolidation or Distribution jobs. Destination agents are waiting for source agents to index the files and build the folder tree before transfer.

no peers

means that the agents are not connected to each other and are not connected to at least one other Agent in the same job. This status is countered as "working" or "in progress" in filters and overviews.
See here for more details about connectivity and ways to troubleshoot it. 

indexing

the Agent scans the files. It might be initial folder scan that agents do right after they're added to the job, or scanning the new/updated files that were dropped into the sync folder, or periodic scan (either scheduled or manual). 

For initial scan check columns "Files" and "Size" as the counters shall increase as Agent scans more files.

Other agents in the job run might be showing status 'syncing' or "synced" if all already scanned files are downloaded by them, and they're awaiting for the Agent to scan more files.

initial synchronization

Appears on RW Agents in the jobs where a Reference Agent is selected. It means that the Agent is updating local file permissions and the folder tree to match those on the Reference Agent. It is a virtual status and cannot be filtered on job run overview or in the Agents' table in the job run. 

writing acl

This status means that the Agent works on applying the file permissions. This might be lengthy operation in the jobs with millions of files. Together with this status, the Agent also has "Processing file attributes" activity on the Activity tab.

executing pre-indexing script

appears on source agents in Consolidation or Distribution jobs. Means there was pre-indexing trigger configured, and the Agent executes the script. 

syncing / 
downloading

the agent actually transfers the files. The status also appears if the agents copies local files' pieces (instead of transferring them over the network) or does differential sync. 
To see more details about what the Agent is busy with, click on the Agent name and open tab Activity. 

cleaning up destination folder

Appears on destination Agents in Distribution or Consolidation jobs, if the Agent's profile have parameter Delete files absent on source agent (Transfer jobs) set to Yes. This operation is very quick, so this status can be seen pretty rarely - the Agent does not list the files inside subfolders that needs to be cleaned up.  The status may linger for a while if the destination folder is, for example, a network share with millions of files to be cleaned up. 

low priority 

the Agent does not work in this job run because there are other job runs with higher priority.

waiting for scheduled script

refers to post-download or complete triggers in Consolidation or Distribution jobs or script in a Script job. See here for more details about scripts. 

executing post-download script

executing complete script

executing script

archiving script logs

waiting for pre-move script execution

appears starting with v4.1.0 in Distribution jobs with enabled "Before finalizing download" trigger. 

executing pre-move script

appears starting with v4.1.0 in Distribution jobs with enabled "Before finalizing download" trigger. 

moving files

appears starting with v4.1.0 in Distribution jobs with enabled "Before finalizing download" trigger. The destination Agents completed the "Before finalizing download" trigger and are completing the download by moving the file to their locations. It's expected to be a near-immediate operation, though might take a while on large dataset on slow storages.

resolving  peers availability before cleanup

appears starting with v4.1.0 in Consolidation or Distribution jobs with enabled option to delete files from source. The source Agent verifies if the files were delivered to all destination Agents before proceeding with the deletion.

cleaning up source folder

appears starting with v4.1.0 in Consolidation or Distribution jobs with enabled option to delete files from source. The source Agent is actually moving the files to Archive (if enabled) or skipping the Archive. It's expected to be a near-immediate operation, though might take a while on large dataset on slow storages.

seeding

appears on Consolidation or Distribution jobs. Once the Agent downloads all the files from the source, it may help and distribute these files to other destinations due to peer-to-peer nature of Resilio Connect, provided there's connection between the destinations.

synced

means that the agent has downloaded all the files that are in its active download queue. This status may be tricky as it's closely related to other statuses (indexing, syncing) and the following shall be kept in mind:
- 'synced' status appears if source of files is still indexing the files (and shows such status), while other agents downloaded all the already indexed files.

- the source of files will show 'synced' if there's nothing for it to download.

- there's no other agent to download files from. Even though some files might be not downloaded yet, the Agent with these files is no longer in the mesh or is not connected.

Look at the columns "Files" and "Size", and compare the "X of Y" (X = the files this Agent has, Y = total files in the tree).

successfully finished

appears on Consolidation or Distribution jobs. Means that the Agent downloaded the files from source and executed its trigger. Mind that with 'Skip file errors' enabled in Agent profile, the Agent will still report this status even though some files might have failed, no error message will be reported. 

paused

the Agent is paused. 

processing files

it's a general status meaning that the Agent works with folder tree: inserts entries in the folder tree, creates empty directories on the disk (creates folder tree on disk), symbolic links, empty files, updates files' timestamps, creates placeholders, etc.  

deploying policy

the Agent received the policy from the Management Console and is getting ready to start the job. Policy - is the set of Profile settings, and the job configuration itself. Agent creates the directory to sync, creates .sync service folder, takes disk probes, sets scheduler is necessary, searches for other agents in the job, etc.

aborted

The job run was aborted, either by timeout, or stopped manually. It will also be aborted if files change on source Agent and parameter "Skip file errors" in the Profile is False.

path not selected

means that Admin selected "Ask user" for this job's path, and the user hasn't yet selected the job folder directory. 

failover

was introduced in v4.0.0 together with HA groups. The agents are in the failover process

following

was introduced in v4.0.0 together with HA groups. the Agent is the follower in the HA group and is not actively participating in data transfer.

all done! All files queued to be synced are synced. 

some files are being synced.  If agent is alone in the job and has status 'no peers' in job run, it's also counted as 'in progress'. This status is shown till agents verify that all files are indeed synced. Then it changes to 'synced'. If this status does not go away, it indicates that some files got stuck and cannot be synced, see here for possible reasons.

agent  has been disconnected from MC for that many hours\days\months.  It does not necessarily mean that it's also disconnected from other agents in a job. 

a problem that the Agent has encountered. This status is clickable and shows the error message with link to KB explaining it.

license does not cover this agent. There may be not enough server/desktop units or mobile agents in the license, or license subscription has expired.

agent is not taking part in any currently running job, i.e. not in a Sync job and/or all its transfer Job Runs have finished.  Error status overwrites this one.

Appears in agent details -> Job runs. Means that agent is not doing this job cause this job's priority is lower that some other's.

It is required to restart the Agent process, for example, for a new Profile parameter to be applied.

Agent is paused by scheduler or user from Agent UI.

files not finished syncing. This status is shown till agents verify that all files are indeed synced. Then it changes to green checkmark. If this status does not go away, it indicates that some files got stuck and cannot be synced, see here for possible reasons.

all done! The distribution/consolidation job run also shows this status of scrip fails with an error on all destination agents (v3.0.0)

Idle

Synchronisation jobs. All files that were in queue for synchronisation are synced between online Agents 

The job run was aborted, either by an error, scheduler or manually. It will also be aborted if files change on source Agent and parameter "Skip file errors" in the Profile is False.

appears in a separate column. an agent encountered an error when performing the job. It's clickable and shows the agent name and the error message.

 Appears in Job Run details -> Agents. Means that for an agent this job run is of lower priority at the moment. 

The job run is paused

The job run timed out by the parameter in the Job Profile.

there are no currently active Job Runs - either job has not yet been launched or all runs are finished or aborted.

there is an active Job Run. Valid for transfer jobs

this job is working. Valid for Sync jobs. Note, even if nothing is being synced right now, and its Job Run shows status 'synced', the job itself will have status 'in progress' due to the nature of Sync job.

Synced 

Synchornization job. All files that were in queue for synchronisation are synced between online Agents 

 Job is configured to run on schedule - either periodically or at a specific time. See column "Schedule" to see it.