When an Agent participates in a job, it creates a hidden service directory .sync in the root of the folder. It's created by each agent in a Sync or Script job, and by destination agents in Consolidation & Distribution job.
The crucial file inside .sync is the identifier of the folder - ID file, by which the agent knows that it's the directory that shall be synced. All agents in one job haму different ID file.
If anything happens with the ID file, an error is raised by an agent and data delivery stops. There might be several cases when an error about it will appear.
Agent won't recover from this error. To fix these errors, eliminate the causing factor and restart the agent in a job run affected.
1. Not enough permissions to create identifying .sync/ID file for this shared folder
The error means that agent was not even able to create ID file. Basically, it means that the user that runs the agent may be lacking read-write access in the selected folder. Revise the folder preferences and fix permissions. If this is a mounted folder - revise mount permissions, too.
However, agent won't recover from the error - after fixing permissions remove the agent from the job and add it back again; or use "Restart on agents" button in the job run.
2. Share's identifying .sync/ID file is missing
The error means that ID is simply deleted. Unfortunately, the Agent cannot know what might have deleted it and the best fix here is to remove the agent from the job and add it again so that it creates new ID. Do not attempt to copy ID file from another job or another peer.
Another possible reason for missing ID file is that the job was created BEFORE mounting the drive where job should keep the data. As a result, the ID file is hidden below the mount point. It is recommended to unmount the drive, remove .sync/ID file, mount it again and re-add agent to the job; or use "Restart on agents" button in the job run.
At the same time, error "Service files missing" appears in Agent UI and means the same
3. Share's identifying .sync/ID file is broken
Basically it means that the content of ID file has changed for the agent. The most frequent reason for it is that this folder is used for another job by this agent and thus ID file has new job's identifier recorded there. It's highly advisable not to point the agent into same directory for different job. The fix here is to reorganise the jobs so that agent syncs different directories with each job. You might want to contact support to get help on how to achieve your setup goals.
It's also possible that the ID file was just corrupt and is now filled with rubbish symbols or zeroes. Remove the agent from the job and add it back again for ID file to be recreated; or use "Restart on agents" button in the job run.