Exception Handling when Task Outcome Content Types are deleted
When creating custom Task Outcomes in a Task Action, a new Content type is automatically being created at Site Level and added in the Workflow Task list.
We had a heavy workflow with different Tasks and used this "custom Outcomes" until we realized it would be more efficient with custom Content types for our outcomes.
We refactored the workflow, forgetting a couple of Task Actions, and deleted automatically generated Content Types that were still in use.
The designer won't open the workflow anymore. The Null Pointer Exception is not caught.
Hours of work were lost as we couldn't save the Workflow and had to re-import an older version.