# How to remove Good\_WritePending overlay in runtime

**URL:** <https://forum.inductiveautomation.com/t/how-to-remove-good-writepending-overlay-in-runtime/82494>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [November 29, 2023, 9:00pm UTC](https://forum.inductiveautomation.com/t/how-to-remove-good-writepending-overlay-in-runtime/82494 "2023-11-29T21:00:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kenneth\_Wainwright](https://avatars.discourse-cdn.com/v4/letter/k/e99b99/32.png) [@Kenneth\_Wainwright](https://forum.inductiveautomation.com/u/Kenneth_Wainwright)\
**Post date:** [November 29, 2023, 9:00pm UTC](https://forum.inductiveautomation.com/t/how-to-remove-good-writepending-overlay-in-runtime/82494/1 "2023-11-29T21:00:10Z")

</div>

I am using indirect bidirectional tags and the "Good\_WritePending" overlay that pops up every time I do a write drives me nuts. I see no reason why an operator needs to be told that everything is working. Is there a way to disable this?

I have looked around a bit and searched through the forums, and I can't get it to disappear. I have tried "Overlay Opt-Out" set to true and that does not work (and besides, I don't want to disable overlays for bad quality). I have even searched the JSON for my views to make sure I hit every possible place this opt-out could be set. Still there.

Any guidance here would be greatly appreciated!

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/9/699e78c766271d5be5490e9fdd7766a0d3b26c2c.png)

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [November 29, 2023, 9:07pm UTC](https://forum.inductiveautomation.com/t/how-to-remove-good-writepending-overlay-in-runtime/82494/2 "2023-11-29T21:07:30Z")

</div>

> [@Kenneth\_Wainwright](#):
>
> I see no reason why an operator needs to be told that everything is working.

Really?

The good\_WritePending is informing the operator that the command has been issued but not verified. Understanding this could be critical in certain applications - if communication is lost or intermittent, for example.

How long does the overlay persist? Is this related to the tag's scan class?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [November 29, 2023, 9:15pm UTC](https://forum.inductiveautomation.com/t/how-to-remove-good-writepending-overlay-in-runtime/82494/3 "2023-11-29T21:15:53Z")

</div>

If you truly do not need the confirmation on those tags, you can use optimistic writes in the tag group (or a dedicated tag group for this purpose).

---

<div class="post-metadata">

**Author:** ![Kenneth\_Wainwright](https://avatars.discourse-cdn.com/v4/letter/k/e99b99/32.png) [@Kenneth\_Wainwright](https://forum.inductiveautomation.com/u/Kenneth_Wainwright)\
**Post date:** [November 29, 2023, 10:14pm UTC](https://forum.inductiveautomation.com/t/how-to-remove-good-writepending-overlay-in-runtime/82494/4 "2023-11-29T22:14:38Z")

</div>

I suppose I should change my statement to "In my application, I have no need for this information, and it is likely to cause confusion and late night calls". Our operators just want to know when something is wrong.

---

<div class="post-metadata">

**Author:** ![Kenneth\_Wainwright](https://avatars.discourse-cdn.com/v4/letter/k/e99b99/32.png) [@Kenneth\_Wainwright](https://forum.inductiveautomation.com/u/Kenneth_Wainwright)\
**Post date:** [November 29, 2023, 10:17pm UTC](https://forum.inductiveautomation.com/t/how-to-remove-good-writepending-overlay-in-runtime/82494/5 "2023-11-29T22:17:31Z")

</div>

This is the solution! Thank you so much. I am new to ignition but very impressed with the platform, and this seemed like such an obvious oversight. Our network is entirely local, so losing the annoyance is worth an unlikely dropped command.
