Thanks for the response.  I have already done #1 - I changed the polling interval  to 5 minutes from 1 minute. It helps.  I would prefer not to do #2, since it requires significant  changes to the overall design of a rather complex process.  And adds A LOT of code to around 300 jobs.  Is the the supression of this particular error message  something that could be included in the options menu in a  future release?  Arthur  : You really got only 2 options: 1. Increase event checking time so that  : messages "already queued" don't apper too often.  : or  : 2. Disable automatic logging for these jobs, and then add custom loggin into  : notification events enabling start/finish and error events with script  : type. In the script code the following  : ChooseCase "@V"event"", END_CHOOSE  : Case "START"  : LoagAddMessageEx "INFO", @V"job_id",  : "@V"job_name"", "Job started"  : Case "FINISH"  : LoagAddMessageEx "INFO", @V"job_id",  : "@V"job_name"", "Job finished"  : CaseElse  : "LoagAddMessageEx "INFO", @V"job_id",  : "@V"job_name"", "Job Error"  : END CHOOSE:   
   |