<div>
<div>Hi Mark,</div>
<div> </div>
<div>thanks for the help. I wasn't able to test the actual problem (about production system performance with a mass IDoc deletion run creating thousands of events in a small time) at first but testing it with another event creator & workflow I managed to recreate the error.
</div>
<div> </div>
<div>When testing I could see the event was actually created and caught by the workflow immediately, so everything was ok behind the scenes. It was just the workflow log which showed the start event time to be one hour late, the event log itself showed ok.
</div>
<div> </div>
<div>So I'll probably be in touch with OSS about this...</div>
<div> </div>
<div>Thanks,</div>
<div>Mikko</div>
<div><br>Date: Thu, 16 Nov 2006 13:27:59 +0000<br>From: "Mark Pyc" <<a href="mailto:mark.pyc@gmail.com">mark.pyc@gmail.com</a>><br>Subject: Re: Work item creation delay after event received<br>To: "SAP Workflow Users' Group" <
<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>Message-ID:<br> <<a href="mailto:23f0a78a0611160527i20409503ke6c00069445dba19@mail.gmail.com">23f0a78a0611160527i20409503ke6c00069445dba19@mail.gmail.com
</a>><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>G'day Mikko,<br><br>Does the Event Queue form part of your solution? Could it be the user for<br>scheduled jobs for event delivery that has a different timezone?
<br><br>Just stabbing in the dark.<br><br>Have fun,<br>Mark</div></div>