All pipelines are inactive but the alarm module is installed and I can send myself using the configured twilio account. Pipelines have been working great for the last 2 years.
Active=false on this status screen only means there are not currently any alarms at any of the blocks/stages in that pipeline.
1 Like
Thats great to know. Unfortunatly we also aren't getting any text alarms unless we manually go send ourselves one using the configured twilio account.
Manually as in using the Twilio web interface? A test alarm? system.twilio.sendSms?
No sorry, using alarm pipeline with a test tag on the central gateways default provider
. We have 70+ remote sites and have thousands of alarms configured and we haven't changed any settings but we did add a redudant backend which messed up some stuff where we had to reset the UUID to get gateways to connect. However, the gateways with teh tags that should be alarming send tags just fine.
From one of the remote sites
Okay, so it appears you have some kind of Gateway Network issue right now... could be related to the UUID stuff you just mentioned.
Probably best to get a real support ticket going.
