# Error processing edit for tag path - MQTT Engine

**URL:** <https://forum.inductiveautomation.com/t/error-processing-edit-for-tag-path-mqtt-engine/111866>\
**Category:** Ignition\
**Tags:** designer, ignition83\
**Created:** [October 31, 2025, 6:11pm UTC](https://forum.inductiveautomation.com/t/error-processing-edit-for-tag-path-mqtt-engine/111866 "2025-10-31T18:11:21Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![gabosm](https://avatars.discourse-cdn.com/v4/letter/g/ecd19e/32.png) [@gabosm](https://forum.inductiveautomation.com/u/gabosm)\
**Post date:** [November 2, 2025, 6:25pm UTC](https://forum.inductiveautomation.com/t/error-processing-edit-for-tag-path-mqtt-engine/111866/2 "2025-11-02T18:25:13Z")

</div>

I ended up getting things working again by deleting the Custom Namespace entry. In order to do this, I had to first delete all UDT tags references, along with the namespace root folder that the MQTT Engine creates. This time while configuring the new namespace, I have narrowed the scope of the subscription to “application/26cff63b-1b2c-429b-8210-fc3985035143/device/+/event/up” which should only return the uplink payload data. With the previous scope “application/26cff63b-1b2c-429b-8210-fc3985035143/#” it would return every piece of MQTT data in the application, including downlink data, which likely resulted in different or overwritten tags when a device goes out of range and then reconnects.

This post helped provide some insight: [MQTT Publish Error - #7 by wes0johnson](https://forum.inductiveautomation.com/t/mqtt-publish-error/46072/7)

---

_[View the full topic](https://forum.inductiveautomation.com/t/error-processing-edit-for-tag-path-mqtt-engine/111866)._