I have seen elsewhere, that for whatever evil reason, SP2010 list workflows cannot be triggered by the delete of a list item. Glad the SP dev team didn't design soda machines or you'd never have a CHANGE slot or get your dollar back if it was too wrinkled.
Anyhow, I'm still in need of what really should be baked into the product, a means of firing off a workflow when a list item has been deleted. The workflow being fired will be counting the number of list items meeting a criteria and updating another list, so this is a case where a social engineering solution (e.g. "use an Alert Me instead") won't do.
Sorry if this sounds more like a rant, but haven't the SP dev folks heard of CRUD operations? The "D" is just as valid as the "CRU" part. And that whole order-of-operation excuse I read over on technet is baloney. If SP allows me to delete an item from a list, then obviously SP is aware of the request to delete something, and thus should be able to fire off a workflow in response. Okay, enough ranting.
Is there any way of firing off a list workflow based on a list item delete, without it looking like it belongs on thereifixedit.com?