# How to debug a DEE not triggered via a GUI action

**URL:** <https://community.criticalmanufacturing.com/t/how-to-debug-a-dee-not-triggered-via-a-gui-action/665>\
**Category:** Extensibility\
**Tags:** v11.3, business-rules\
**Created:** [June 7, 2023, 11:45am UTC](https://community.criticalmanufacturing.com/t/how-to-debug-a-dee-not-triggered-via-a-gui-action/665 "2023-06-07T11:45:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ronny\_otto](https://avatars.discourse-cdn.com/v4/letter/r/ad7895/32.png) [@ronny\_otto](https://community.criticalmanufacturing.com/u/ronny_otto)\
**Post date:** [June 7, 2023, 11:45am UTC](https://community.criticalmanufacturing.com/t/how-to-debug-a-dee-not-triggered-via-a-gui-action/665/1 "2023-06-07T11:45:38Z")

</div>

Hi,

We recently tried to debug a DEE responsible to send notifications on a resource state change (FHResourceStateChangesNotificationProcess - and also a new DEE listening to similar ActionGroups).

To enable recognizing the state changes we added a new ActionGroup - and also listen to existing ones:  
BusinessObjects.Resource.AdjustState.Pre  
BusinessObjects.Resource.AdjustState.Post

The DEE is correctly triggered when changing the states. And also sends out notification etc.

But when trying to debug the DEE by setting breakpoints in VS … this is ignored.

Executing the DEE via the Website it correctly stops at the breakpoint.

That DEE is also triggered via listening to BusinessObjects.Resource.LogEvent.Post.  
When changing a resource state via GUI - the breakpoint is also triggered.

SO: when triggered by a nongui event, it seems to ignore the set breakpoints.

Is this something currently not working in the MES - or a limitation of c# (and the way the DEEs are executed)?

Running MES version is 9.1.8.

Regards,

Ronny
