you have any pointers on what might be causing this? I spent some time looking at the code, but cannot figure out what would cause initial runs to act like this. My best guess is its something to do w the EventAdmin, but the call to update is synchronous so that doesnt make sense. Its also extra hard to debug since it happens once every few hours.
This issue has bitten me a few times of late; where the previous fiddle was some long-running op or something that changes data.
If this seems like something we can't put a proper fix in place in next release, I vote for putting a temporary fix in place that deleted the compiled aem fiddle script under /var/classes/... servlet on load. WDYT? This is a nasty bug.