# OEE Downtime Reasons won't delete

**URL:** <https://forum.inductiveautomation.com/t/oee-downtime-reasons-wont-delete/20481>\
**Category:** General Discussion\
**Created:** [November 1, 2018, 3:09pm UTC](https://forum.inductiveautomation.com/t/oee-downtime-reasons-wont-delete/20481 "2018-11-01T15:09:17Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![ngadow](https://avatars.discourse-cdn.com/v4/letter/n/22d042/32.png) [@ngadow](https://forum.inductiveautomation.com/u/ngadow)\
**Post date:** [November 1, 2018, 3:09pm UTC](https://forum.inductiveautomation.com/t/oee-downtime-reasons-wont-delete/20481/1 "2018-11-01T15:09:17Z")

</div>

I’m having a problem when I delete a downtime reason code. I can delete it no problem - then save the project. The original reason code still shows up in my list. Even when I double check that it’s out of the Production Module. I’ve even tried deleting everything and importing the updated list - and the deleted ones still show up.

Any ideas on what to try next?

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/f/f2d58d007a9a8fd29a6033e1a28da927b67ebecb.png)

---

<div class="post-metadata">

**Author:** ![ethomason](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ethomason/32/43338_2.png) [@ethomason](https://forum.inductiveautomation.com/u/ethomason)\
**Post date:** [November 1, 2018, 3:42pm UTC](https://forum.inductiveautomation.com/t/oee-downtime-reasons-wont-delete/20481/2 "2018-11-01T15:42:14Z")

</div>

Restart the module ?

---

<div class="post-metadata">

**Author:** ![ngadow](https://avatars.discourse-cdn.com/v4/letter/n/22d042/32.png) [@ngadow](https://forum.inductiveautomation.com/u/ngadow)\
**Post date:** [November 1, 2018, 3:57pm UTC](https://forum.inductiveautomation.com/t/oee-downtime-reasons-wont-delete/20481/3 "2018-11-01T15:57:24Z")

</div>

I restarted it - closed everything, etc… the old one is still in there.

---

<div class="post-metadata">

**Author:** ![ethomason](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ethomason/32/43338_2.png) [@ethomason](https://forum.inductiveautomation.com/u/ethomason)\
**Post date:** [November 1, 2018, 4:19pm UTC](https://forum.inductiveautomation.com/t/oee-downtime-reasons-wont-delete/20481/4 "2018-11-01T16:19:05Z")

</div>

I would contact Sepasoft support then.

---

<div class="post-metadata">

**Author:** ![ngadow](https://avatars.discourse-cdn.com/v4/letter/n/22d042/32.png) [@ngadow](https://forum.inductiveautomation.com/u/ngadow)\
**Post date:** [November 1, 2018, 5:12pm UTC](https://forum.inductiveautomation.com/t/oee-downtime-reasons-wont-delete/20481/5 "2018-11-01T17:12:59Z")

</div>

Yep I have a ticket in with them. I’m just assuming it’s a global problem and was thinking others may have seen it and hopefully had a workaround.  
Thanks

---

<div class="post-metadata">

**Author:** ![Paullys50](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paullys50/32/3324_2.png) [@Paullys50](https://forum.inductiveautomation.com/u/Paullys50)\
**Post date:** [November 1, 2018, 5:37pm UTC](https://forum.inductiveautomation.com/t/oee-downtime-reasons-wont-delete/20481/6 "2018-11-01T17:37:42Z")

</div>

Is this OEE1.0 or OEE2.0?

---

<div class="post-metadata">

**Author:** ![ngadow](https://avatars.discourse-cdn.com/v4/letter/n/22d042/32.png) [@ngadow](https://forum.inductiveautomation.com/u/ngadow)\
**Post date:** [November 1, 2018, 5:52pm UTC](https://forum.inductiveautomation.com/t/oee-downtime-reasons-wont-delete/20481/7 "2018-11-01T17:52:00Z")

</div>

It’s OEE version 1.0

---

<div class="post-metadata">

**Author:** ![ngadow](https://avatars.discourse-cdn.com/v4/letter/n/22d042/32.png) [@ngadow](https://forum.inductiveautomation.com/u/ngadow)\
**Post date:** [November 1, 2018, 6:03pm UTC](https://forum.inductiveautomation.com/t/oee-downtime-reasons-wont-delete/20481/8 "2018-11-01T18:03:36Z")

</div>

Here is the reply from SepaSoft - It answers the question but still makes me a little sad. When I tested his theory using SepaSofts slider the correct values showed up.

Hi Natalie,  
 It appears you are using your own query to get the downtime codes?  
 How are you getting that data?  
I checked with the developer and in OEE V1 the code persists in the DB for historical access. The downtime table gets the list from the Downtime Codes existing in the internal representation of the production model.  
Currently, we do not support a way to get that list via scripting directly. The intent was to use the supplied downtime table component to manage downtime events. Although this component is based on, and appears as, a standard table it has a large amount of functionality and event manipulation built-in. In OEE V1 these functions are not exposed outside of the component, unfortunately.
