# Uncaught Throwable during notification - simple looping alarm pipeline **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [November 28, 2024, 12:40am UTC](https://forum.inductiveautomation.com/t/uncaught-throwable-during-notification-simple-looping-alarm-pipeline/99205 "2024-11-28T00:40:54Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![AaronJust](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/aaronjust/32/47009_2.png) [@AaronJust](https://forum.inductiveautomation.com/u/AaronJust)\ **Post date:** [November 28, 2024, 12:40am UTC](https://forum.inductiveautomation.com/t/uncaught-throwable-during-notification-simple-looping-alarm-pipeline/99205/1 "2024-11-28T00:40:54Z")
I am trying to create a simple notification pipeline which escalates an alarm only outside of business hours. The pipeline looks like this: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/3/237b5419a588613a423a3fd593773677f46fce04.png) I believe the expression evaluates correctly and loops through the delay block in 'business hours' or redirects to the notification block 'out of hours', however I only ever get one notification, and then the following warning on repeat in the pipeline logs: Uncaught Throwable during notification. > **Stack Trace** > > java.lang.NullPointerException: Cannot read the array length because "" is null > > at com.inductiveautomation.ignition.alarming.pipelines.blocks.NotificationBlock$NotificationContextImpl.profiles(NotificationBlock.java:634) > > at com.inductiveautomation.ignition.alarming.pipelines.blocks.NotificationBlock$NotificationContextImpl.profile(NotificationBlock.java:598) > > at com.inductiveautomation.ignition.alarming.pipelines.blocks.NotificationBlock$NotificationContextImpl.run(NotificationBlock.java:553) > > at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$ThrowableCatchingRunnable.run(BasicExecutionEngine.java:550) > > at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) > > at java.base/java.util.concurrent.FutureTask.run(Unknown Source) > > at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) > > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) > > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > > at java.base/java.lang.Thread.run(Unknown Source) Running the same alarm into a default pipeline that literally just has the alarm notification seems to work fine. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/3/93b2c267773db389d8661d97cf8544ca862c4764.png) Any suggestions appreciated. Gateway is Ignition Maker Edition 8.1.44 running on a Raspberry Pi 4. ---
**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:** [November 28, 2024, 1:19am UTC](https://forum.inductiveautomation.com/t/uncaught-throwable-during-notification-simple-looping-alarm-pipeline/99205/2 "2024-11-28T01:19:57Z")
I don't know why it doesn't error out on the simple flow, but from what I can see it looks to be because there is no notification profile configured. ---
**Author:** ![AaronJust](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/aaronjust/32/47009_2.png) [@AaronJust](https://forum.inductiveautomation.com/u/AaronJust)\ **Post date:** [November 28, 2024, 1:38am UTC](https://forum.inductiveautomation.com/t/uncaught-throwable-during-notification-simple-looping-alarm-pipeline/99205/3 "2024-11-28T01:38:04Z")
I noticed that too but saw another forum post that suggested that if you only have a simple one way notification profile configured then it doesn’t show up, which is the case for me. I can not select a profile in designer. ---
**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:** [November 28, 2024, 1:46am UTC](https://forum.inductiveautomation.com/t/uncaught-throwable-during-notification-simple-looping-alarm-pipeline/99205/4 "2024-11-28T01:46:01Z")
The simple one way profile is not compatible with the pipelines. It's a direct alarm to email setup for simple notification scenarios. ---
**Author:** ![AaronJust](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/aaronjust/32/47009_2.png) [@AaronJust](https://forum.inductiveautomation.com/u/AaronJust)\ **Post date:** [November 28, 2024, 5:35am UTC](https://forum.inductiveautomation.com/t/uncaught-throwable-during-notification-simple-looping-alarm-pipeline/99205/5 "2024-11-28T05:35:57Z")
OK thanks for that information, I'll change over the configuration. What gets me, I'm sure I put that direct configuration in without the loop and it didn't cause the null pointer exception in the logs, which made me think I was using that notification pipeline instead of just the generic simple notification profile. ---
**Author:** ![AaronJust](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/aaronjust/32/47009_2.png) [@AaronJust](https://forum.inductiveautomation.com/u/AaronJust)\ **Post date:** [November 28, 2024, 5:47am UTC](https://forum.inductiveautomation.com/t/uncaught-throwable-during-notification-simple-looping-alarm-pipeline/99205/6 "2024-11-28T05:47:54Z")
Used the same email profile to create an email notification profile instead of a simple one way email profile, assigned it to the pipeline, and of course all is well. Thank you very much for your assistance 🙂