https://devzone.nordicsemi.com/f/nordic-q-a/55027/bsdlib-recoverable-error-3This error always stop the &quot;mqtt_simple&quot; application. I have tried modem versions 1.0.1 and 1.1.0, SDK versions v1.0.0 and v1.1.0 and added this code to system_nrf9160.c - but nothing seem to fix this bug. I am running towards a local mqtt serveren-USTelligent Community 13Tue, 03 Dec 2019 12:33:17 GMThttps://devzone.nordicsemi.com/thread/223319?ContentTypeID=1Tue, 03 Dec 2019 12:33:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:ce879eab-ca85-49eb-a0bb-b8388a4bcee2Hakon<p>Hey,</p> <p>try changing CONFIG_MQTT_KEEPALIVE to once a minute.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/222901?ContentTypeID=1Sun, 01 Dec 2019 08:24:20 GMT137ad170-7792-4731-bb38-c0d22fbe4515:218b58ad-6c0a-492e-a85f-5ca42a751fcfperf<p>I have some additional observations that are rather strange:</p> <p>The application may run flawlessly for some rounds of sub/pub&#39;s, then this error 3 suddenly hits. After that, there are no further output on the terminal emulator (Termite) but the application continues to act on publications and publish its value. The application stops mysteriously (and quietly) after some further sub/pub rounds. I can see this because I have an mqtt client that monitors the publications of the server and the r35/iotpubPer/topic updates after r35/temperaturer/ute/UteTemp is updated.</p> <p>How can this error 3 shut down&nbsp;printk output?&nbsp;</p><div style="clear:both;"></div>