Uncaught Throwable during notification - simple looping alarm pipeline

Ignition
1

I am trying to create a simple notification pipeline which escalates an alarm only outside of business hours.

The pipeline looks like this:

image
image553×376 16 KB

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
image311×142 5.42 KB

Any suggestions appreciated.

Gateway is Ignition Maker Edition 8.1.44 running on a Raspberry Pi 4.

2

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.

3

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.

4

The simple one way profile is not compatible with the pipelines. It's a direct alarm to email setup for simple notification scenarios.

5

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.

6

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 :slight_smile: