# No AlarmNotificationProfileType 'SlackType' found

**URL:** <https://forum.inductiveautomation.com/t/no-alarmnotificationprofiletype-slacktype-found/79487>\
**Category:** Module Development\
**Created:** [September 22, 2023, 12:15am UTC](https://forum.inductiveautomation.com/t/no-alarmnotificationprofiletype-slacktype-found/79487 "2023-09-22T00:15:51Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![glennr](https://avatars.discourse-cdn.com/v4/letter/g/c89c15/32.png) [@glennr](https://forum.inductiveautomation.com/u/glennr)\
**Post date:** [September 22, 2023, 12:15am UTC](https://forum.inductiveautomation.com/t/no-alarmnotificationprofiletype-slacktype-found/79487/1 "2023-09-22T00:15:51Z")

</div>

Hi,

I'm trying to make an alarm notification module that uses a REST to SMS service. I've copied and modified the slack alarm notification example from github but neither are working.

I'm seeing this in the log for the slack module and similar for my modified copy of it:

`No AlarmNotificationProfileType 'SlackType' found, using NoOpProfile. module-name=Slack Alarm Notification Example, alarm-notification-profile=Slack`

Is this error causing it to not work? How do I fix it?

Ignition version 8.1.32 on Fedora 37.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [September 22, 2023, 1:51am UTC](https://forum.inductiveautomation.com/t/no-alarmnotificationprofiletype-slacktype-found/79487/2 "2023-09-22T01:51:46Z")

</div>

This message means there's a profile instance that has been created of type 'SlackType' but for whatever reason at this point in time no module has registered an extension point of that type.

You'll probably have to share some code or whatever modifications you've made.

---

<div class="post-metadata">

**Author:** ![glennr](https://avatars.discourse-cdn.com/v4/letter/g/c89c15/32.png) [@glennr](https://forum.inductiveautomation.com/u/glennr)\
**Post date:** [September 22, 2023, 2:06am UTC](https://forum.inductiveautomation.com/t/no-alarmnotificationprofiletype-slacktype-found/79487/3 "2023-09-22T02:06:50Z")

</div>

This is with the unmodified example code from GitHub.

```auto
https://github.com/inductiveautomation/ignition-sdk-examples/tree/master/slack-alarm-notification

```

I have added and removed the module more than once. Could that be the issue?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 22, 2023, 11:36am UTC](https://forum.inductiveautomation.com/t/no-alarmnotificationprofiletype-slacktype-found/79487/4 "2023-09-22T11:36:07Z")

</div>

> [@glennr](#):
>
> Could that be the issue?

Possibly. If the module has a life cycle bug, such can often be worked around by restarting the gateway.

---

<div class="post-metadata">

**Author:** ![glennr](https://avatars.discourse-cdn.com/v4/letter/g/c89c15/32.png) [@glennr](https://forum.inductiveautomation.com/u/glennr)\
**Post date:** [September 23, 2023, 10:41pm UTC](https://forum.inductiveautomation.com/t/no-alarmnotificationprofiletype-slacktype-found/79487/5 "2023-09-23T22:41:54Z")

</div>

Thank you. Restarting the gateway seems to make things work again. It seems a bit random as to whether that is required or not as sometimes I can reinstall the module after making changes and it doesn't have the error.

---

<div class="post-metadata">

**Author:** ![glennr](https://avatars.discourse-cdn.com/v4/letter/g/c89c15/32.png) [@glennr](https://forum.inductiveautomation.com/u/glennr)\
**Post date:** [September 28, 2023, 8:44pm UTC](https://forum.inductiveautomation.com/t/no-alarmnotificationprofiletype-slacktype-found/79487/6 "2023-09-28T20:44:12Z")

</div>

Something else I've noticed is that on module reinstall sometimes the i18n strings don't load. Restarting the module fixes this.
