<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Publish timeout handler of one model called during publish timeout handler of another model</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/62159/publish-timeout-handler-of-one-model-called-during-publish-timeout-handler-of-another-model</link><description>Hi, 
 I just have a small question: say I have two models, both with publish timeout intervals configured. After some time, one model&amp;#39;s publish timeout handler is called. Could it be that the model&amp;#39;s publish timeout handler is called during the handling</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 04 Jun 2020 15:17:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/62159/publish-timeout-handler-of-one-model-called-during-publish-timeout-handler-of-another-model" /><item><title>RE: Publish timeout handler of one model called during publish timeout handler of another model</title><link>https://devzone.nordicsemi.com/thread/253350?ContentTypeID=1</link><pubDate>Thu, 04 Jun 2020 15:17:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:558fbbd2-9b08-4ae6-ad9e-93e78b166611</guid><dc:creator>Mathias</dc:creator><description>&lt;p&gt;Ok, thanks for the explanation!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Publish timeout handler of one model called during publish timeout handler of another model</title><link>https://devzone.nordicsemi.com/thread/253342?ContentTypeID=1</link><pubDate>Thu, 04 Jun 2020 14:55:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cc2772ab-5ca4-4a7f-80d9-68934df30d62</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Mathias,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;No, they will run at the same priority level (either&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v4.1.0/group__MESH__DEFINES__API.html#ga1f773910993da2538b64bd3d6875a498"&gt;NRF_MESH_IRQ_PRIORITY_LOWEST&lt;/a&gt;&amp;nbsp;or&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v4.1.0/group__MESH__DEFINES__API.html#ga3c75e81adeb76c025c403caed6fae531"&gt;NRF_MESH_IRQ_PRIORITY_THREAD&lt;/a&gt;&amp;nbsp;depends how you configure your mesh stack). So they will not preempt each other. You don&amp;#39;t need to have a semaphore to handle the access. And in addition, using critical region is not allowed when in mesh call back. Have a look here:&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v4.1.0/md_doc_user_guide_mesh_interrupt_priorities.html?cp=7_2_2_5"&gt;https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v4.1.0/md_doc_user_guide_mesh_interrupt_priorities.html?cp=7_2_2_5&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>