# Equipment process PLC to Kepware to CM

**URL:** <https://community.criticalmanufacturing.com/t/equipment-process-plc-to-kepware-to-cm/990>\
**Category:** Integrations\
**Tags:** equipment, v10.2\
**Created:** [November 10, 2026, 9:43am UTC](https://community.criticalmanufacturing.com/t/equipment-process-plc-to-kepware-to-cm/990 "2026-11-10T09:43:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Judi\_Hammond](https://avatars.discourse-cdn.com/v4/letter/j/6a8cbe/32.png) [@Judi\_Hammond](https://community.criticalmanufacturing.com/u/Judi_Hammond)\
**Post date:** [November 10, 2026, 9:43am UTC](https://community.criticalmanufacturing.com/t/equipment-process-plc-to-kepware-to-cm/990/1 "2026-11-10T09:43:06Z")

</div>

We have a process that triggers a DEE but when the DEE fails the board moves to the next station in CM.

What we would like to know if you see anything in this snippet of the code that we missed.

 ![image](https://canada1.discourse-cdn.com/flex050/uploads/community_criticalmanufacturing/original/2X/6/60f4f847f77f9bb1b3a6c0020d26da11f6988cf7.png)

We see in the IoT this error :

#### The data for object

_DII-1188128-5fbc4e0917e84584a84e7a2b422ee97e  
of type DurablesBOMInstanceItem  
has changed since last viewed.  
Please refresh the object._

But CM still moved it to the next station. This DEE snippet is the DEE called in the IOT flow.

Any input or suggestions are appreciated.

thank you

Judi

---

<div class="post-metadata">

**Author:** ![Ruben\_Ferreira](https://avatars.discourse-cdn.com/v4/letter/r/76d3ee/32.png) [@Ruben\_Ferreira](https://community.criticalmanufacturing.com/u/Ruben_Ferreira)\
**Post date:** [November 10, 2026, 2:46pm UTC](https://community.criticalmanufacturing.com/t/equipment-process-plc-to-kepware-to-cm/990/2 "2026-11-10T14:46:24Z")

</div>

Hello Judi,

Have you checked the Material History to see if this DEE was executed or just evaluated? If the error was thrown as a result of the TrackOut that is called inside the DEE, then it should not take place due to a rollback so I suspect there might be another source for this movement.

Cheers.

---

<div class="post-metadata">

**Author:** ![Ricardo\_Cunha](https://yyz2.discourse-cdn.com/flex050/user_avatar/community.criticalmanufacturing.com/ricardo_cunha/32/1133_2.png) [@Ricardo\_Cunha](https://community.criticalmanufacturing.com/u/Ricardo_Cunha)\
**Post date:** [November 11, 2026, 5:11pm UTC](https://community.criticalmanufacturing.com/t/equipment-process-plc-to-kepware-to-cm/990/3 "2026-11-11T17:11:32Z")

</div>

Hi Judi,

Can you explain the scenario into more detail to understand better why we are catching exceptions from a framework orchestration method? Usually we do not recommend it, but there might a reason behind it.

Thank you,  
Ricardo

---

<div class="post-metadata">

**Author:** ![system](https://yyz2.discourse-cdn.com/flex050/user_avatar/community.criticalmanufacturing.com/system/32/23_2.png) [@system](https://community.criticalmanufacturing.com/u/system)\
**Post date:** [November 16, 2026, 7:25pm UTC](https://community.criticalmanufacturing.com/t/equipment-process-plc-to-kepware-to-cm/990/4 "2026-11-16T19:25:04Z")

</div>

Closed on November 16, 2026, 7:25pm UTC

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
