# MQTT & Historian

**URL:** <https://forum.inductiveautomation.com/t/mqtt-historian/62695>\
**Category:** Ignition\
**Created:** [August 4, 2022, 7:07pm UTC](https://forum.inductiveautomation.com/t/mqtt-historian/62695 "2022-08-04T19:07:56Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [August 4, 2022, 9:14pm UTC](https://forum.inductiveautomation.com/t/mqtt-historian/62695/2 "2022-08-04T21:14:05Z")

</div>

I think this thread discusses your specific question: [[FEATURE] Allow reference tags to receive backfill data from sources like MQTT tags](https://forum.inductiveautomation.com/t/48261)

I’ve not had a chance to check in on this behavior, but there I’m pretty sure there was a point in time in the past where the history was _only_ on the base MQTT tag, requiring some custom functionality to indirect over to it for history queries (associated with your UDT). Last time I worked with this specific scenario was back in the 8.0.x days (and associated MQTT module versions of that time).

EDIT: just for clarity, the situation I mentioned above had History enabled on the MQTT Engine tag (and not the reference tags in the UDT). That used to be the only way I could get the backfill working properly.

---

_[View the full topic](https://forum.inductiveautomation.com/t/mqtt-historian/62695)._