Unforgivable!
For the love of all that’s holy – I’m getting pretty tired of the total lack of error handling in MOSS. The latest one? A workflow that failed to start. Not only that but it failed to start for seemingly no reason. No error messages reported in the log file, nothing on the web page. The workflow itself looked as though it had never been run. Silence. Total abject silence. A silence so deafening one could hear the electrons race thru the CPU.
The reason for the lack of workflow action I found out (after a six hours of messing around) was a now defunct TaskListContentTypeId attribute in the <Workflow> entity located in workflow.xml. Granted the error was mine – don’t know when it became defunct, but defunct it was. However what I find so disturbing is that this situation obviously caused an exception to be thrown somewhere – so why on earth wasn’t it recorded anywhere?
Sheesh…
