# Class cast exception due to different class loaders

**URL:** <https://forum.inductiveautomation.com/t/class-cast-exception-due-to-different-class-loaders/67786>\
**Category:** Module Development\
**Created:** [December 19, 2022, 2:40pm UTC](https://forum.inductiveautomation.com/t/class-cast-exception-due-to-different-class-loaders/67786 "2022-12-19T14:40:16Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![nicholas.robinson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nicholas.robinson/32/22188_2.png) [@nicholas.robinson](https://forum.inductiveautomation.com/u/nicholas.robinson)\
**Post date:** [December 19, 2022, 3:54pm UTC](https://forum.inductiveautomation.com/t/class-cast-exception-due-to-different-class-loaders/67786/8 "2022-12-19T15:54:02Z")

</div>

Right now we have alarms and tags working fine so we'll just be disabling sending of audit data to kafka.

If the module SDK is updated to have a method to remove an audit profile type or have an interface to grab the audit event without having to create a new audit type, we'll come back and update the gateway hook and/or gateway script module.

Added this to the features and ideas page [here](https://inductiveautomation.canny.io/ignition-features-and-ideas/p/audit-profile-lifecycle-methods).

Nick

---

_[View the full topic](https://forum.inductiveautomation.com/t/class-cast-exception-due-to-different-class-loaders/67786)._