From 4698f6474ee1bbce113f4d369ce1cf8707851150 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ferm=C3=ADn=20Gal=C3=A1n=20M=C3=A1rquez?= Date: Wed, 3 Jul 2024 13:33:04 +0200 Subject: [PATCH] Update doc/manuals/orion-api.md Co-authored-by: mapedraza <40356341+mapedraza@users.noreply.github.com> --- doc/manuals/orion-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/manuals/orion-api.md b/doc/manuals/orion-api.md index a32334b2aa..1c1bbc1961 100644 --- a/doc/manuals/orion-api.md +++ b/doc/manuals/orion-api.md @@ -2539,7 +2539,7 @@ In order to overcome this problem, the `evalPriority` metadata can be used to de * `evalPriority` metadata is a number from 1 (first evaluation) to 100000 (last evaluation) * Expressions are evaluated in incresing order of priority -* In case of ties, Orion does not guarantee a particular evaluation order. Thus, expressions in the same priority level must be considered independent or bad things would happen +* In case of ties, Orion does not guarantee a particular evaluation order. Thus, expressions in the same priority level must be considered independent, and expressions using other attributes with the same or lower priority would result in unexpected values. * If no `evalPriority` is set, default 100000 is used * `evalPriority` only has a meaning in `notification.httpCustom.ngsi` in subscriptions. As metadata in regular entities (e.g. an entity created with `POST /v2/entities`) Orion doesn't implements any semantic for it