Eventhandlers don't work if a package is started from a checkpoint - BIG NASTY BUG (I think)

[Yes, I know I keep posting this, and I'm sorry for that. But I want someone to confirm that this is a bug and not by design. I feel it is very very important]

All,

I'd like someone from MS to confirm something for me if possible.

I've just come across a situation where a package that is restarted from a checkpoint fails to execute any of its eventhandlers if those eventhandlers are scoped to a parent container.

Is this a bug or by design? Either way I'm VERY worried about this because this is not in the least bit intuitive. This is the most dangerous bug that I have seen in RTM.

-Jamie

If you want a demo of this happening then download this package: http://blogs.conchango.com/Admin/ImageGallery/blogs.conchango.com/jamie.thomson/20060103Package1.zip

It doesn't need any configuration because there are no connection managers. You can just run it standalone. Run it first time and it will fail but you WILL see msgboxes popped up by the eventhandlers. Go into "Script Task 2" and make the return value "Success" rather than "Failure". Run it a second time. The package will complete successfully but NO msgboxes will pop up from the eventhandlers. They are not executing.

Reply here or email direct with any queries!

Anyone? Anyone?

I'm just going to keep posting this until someone from MS replies. It is NOT hard to repro. Just download the package.

-Jamie