In the modeller, if an intermediate message catch event is added to a Human task then the task is changed to a Service task, the event appears ‘behind’ the task and then the task cannot be selected, changed or deleted. Even if the boundary event is deleted, the Service task stays a ‘zombie’ and cannot be altered. The only way to fix it is to add something like a gateway or event to that task to ‘wake it up’ and make it accessible again as a Human task
Is there some significant to when the event appears under the task as opposed to on top of it? Have I missed something and the modeller is trying to tell me I can’t have message catch events on Script tasks?