Skip to content

Specification of the externalEventID

With this update we correct the behaviour of the externalEventID.

Jason Songhurst
Jason Songhurst Software Engineer
|
1 min.

With this update we correct the behaviour of the externalEventID. Previously, when an alarm was triggered, another event was opened despite the same externalEventID. From now on, we will use the existing event for this as long as it is still open. The specified event name is ignored in this case.

The information is processed in the following order:

If the eventID is specified, we use the open event for the alarm. If the event is already closed, we do not trigger the alarm.

If the externalEventID is specified and an open event with the same ID exists, we trigger in this event. The specified event name is ignored. If no event is open, we open a new one (even if there is already one with the same externalEventID).

If no ID is specified, we open a new event with the specified name and create a new eventID.

AI tools were used to help create this article. Our editorial team completed the final wording and technical review.

Enable customer chat

Our customer chat is provided by Crisp. If you agree, Crisp will load and receive connection data (such as your IP address) and your chat messages. Crisp may use cookies and browser storage. Your agreement is remembered for this browser tab’s session. Without your agreement, Crisp will not load.