I'm no expert but I know procedurally these !SYNCH8 can be bypassed by a CMN Admin. you may want to check with an Admin there, the process is pretty easy.
I'd like to add; there's an Impat Analysis process in CMN you should get familur with. this will generally show the impact and component relationship prior to running the audit, thus catching the error beforehand
most SYNCH8 issues I've seen are due to CICS or DB2 modules not included in the CMN promote process and can be bypassed.
