# Operational data subscriton priority doesn't works

**URL:** <https://dmap-community.ductus.global/t/operational-data-subscriton-priority-doesnt-works/3149>\
**Category:** CDB and CDB API\
**Created:** [July 8, 2020, 7:53am UTC](https://dmap-community.ductus.global/t/operational-data-subscriton-priority-doesnt-works/3149 "2020-07-08T07:53:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ruxob](https://avatars.discourse-cdn.com/v4/letter/r/97f17d/32.png) [@ruxob](https://dmap-community.ductus.global/u/ruxob)\
**Post date:** [July 8, 2020, 7:53am UTC](https://dmap-community.ductus.global/t/operational-data-subscriton-priority-doesnt-works/3149/1 "2020-07-08T07:53:02Z")

</div>

I cannot handle priority on Operational data (except -1).  
How can i avoid this issue and call my Operational node first?  
Is there another way to handle this issue ?

---

<div class="post-metadata">

**Author:** ![greg](https://avatars.discourse-cdn.com/v4/letter/g/71c47a/32.png) [@greg](https://dmap-community.ductus.global/u/greg)\
**Post date:** [July 10, 2020, 2:46pm UTC](https://dmap-community.ductus.global/t/operational-data-subscriton-priority-doesnt-works/3149/2 "2020-07-10T14:46:56Z")

</div>

Are you trying to use cdb\_subscribe()? For operational data, you should use cdb\_oper\_subscribe(). You’ll notice that priority is missing from the input parameters, and as the explanation text says for this API “Priorities are not used for these notifications”. Also take a look at the “Note” for this API, if you want to mix subscriptions to operational data and configuration data on the same subscription socket.