# SDK Changes to HistoryManager

**URL:** <https://forum.inductiveautomation.com/t/sdk-changes-to-historymanager/82446>\
**Category:** Module Development\
**Tags:** ignition81\
**Created:** [November 28, 2023, 8:05pm UTC](https://forum.inductiveautomation.com/t/sdk-changes-to-historymanager/82446 "2023-11-28T20:05:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [November 28, 2023, 8:11pm UTC](https://forum.inductiveautomation.com/t/sdk-changes-to-historymanager/82446/2 "2023-11-28T20:11:05Z")

</div>

I'm pretty sure you're running into the same regression surfaced by another developer implementing a third party historian. It's fixed in 8.1.33.

Described in a bit more detail here: [Nightly 8.1 Changelogs - 2023 - #141 by system](https://forum.inductiveautomation.com/t/nightly-8-1-changelogs-2023/68524/141)

> Tag Historian  
> **IGN-8408: Unable to send tag historical data to the Canary historian.**  
> Fixed an issue where Tag History storage wouldn't be accepted to targeted DataSink if matching Tag History provider didn't exist.

---

_[View the full topic](https://forum.inductiveautomation.com/t/sdk-changes-to-historymanager/82446)._