# Using third party libraries with ignition tags as variables

**URL:** <https://forum.inductiveautomation.com/t/using-third-party-libraries-with-ignition-tags-as-variables/95802>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [September 10, 2024, 2:40pm UTC](https://forum.inductiveautomation.com/t/using-third-party-libraries-with-ignition-tags-as-variables/95802 "2024-09-10T14:40:29Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\
**Post date:** [September 11, 2024, 11:31am UTC](https://forum.inductiveautomation.com/t/using-third-party-libraries-with-ignition-tags-as-variables/95802/15 "2024-09-11T11:31:51Z")

</div>

Can you restart your gateway?

> [@Custom Expression Function not recognized "Unknown Function"](https://forum.inductiveautomation.com/t/custom-expression-function-not-recognized-unknown-function/91206/4):
>
> Interesting. I had a report here in the forum about my Integration Toolkit functions not working for expression tags but everywhere else. That reporter fixed it by restarting their gateway and I never reproduced it. Bug in the tag provider hierarchy, perhaps?

---

_[View the full topic](https://forum.inductiveautomation.com/t/using-third-party-libraries-with-ignition-tags-as-variables/95802)._