Problem With Jobs Dropping Out of Groups

SyncBackSE v6.5.22.0
Windows Server 2008 R2

I've had an issue for awhile now where individual jobs randomly drop out of groups. I've read some of the kb articles on this issue and have taken steps to ensure that SyncBack's profile's aren't locked when jobs run but it's still happening.

To get into more detail, on the domain controller I have several groups, backup (for the domain controller), several replication groups to copy standard icons, tools and scripts around.

Some notes:
1. The source files for the replication jobs aren't even on the domain controller.
2. Only the replication groups (so far) have had the dropout issue.
3. The backup job group *specifically* excludes SyncBack's appdata directory.
4. It doesn't always do it (day to day) and it's very random what jobs fall out of the list.
5. Sometimes it's one job that falls out, sometimes it's a half dozen or somewhere in between.


To try to further ensure that the profiles aren't locked:
1. Recently, I created batch file to run SyncBack jobs with a simple file locking mechanism so replication groups will not run if backup group is running.
2. The backup jobs all use VSS shadow copies for source.


Example:
The SyncBack backup batch file does this:

echo BACKUP > C:\Locks\syncback.lock
cd /d "C:\Program Files (x86)\2BrightSparks\SyncBackSE"
SyncBack.exe -m "Backup"
if exist  C:\Locks\syncback.lock del C:\Locks\syncback.lock

The Replication jobs do this:

(The group name is passed as an argument from Task Scheduler)

if exist C:\Locks\syncback.lock goto :locked
goto :unlocked

:locked
goto :eof

:unlocked
cd /d "C:\Program Files (x86)\2BrightSparks\SyncBackSE"
SyncBack.exe -m "%*"
goto :eof

At this point, I have no idea why it's doing this.
SyncBack's profiles should *never* be locked.