I've been trying to update alarm contents to reformat the message and add some other details to the custom fields. This I can do. But the action of updating the alarm then triggers the script to run again and update the field - and repeats this.
What control is there so the alarm is only processed when it first arrives? There must be something obvious I am missing. It seems the alarm.set() action places the message back on the Nimbus and therefore it gets processed as if it had just arrived.