# Help Needed please: AWX isolated node not registering automatically and  dropping  after 30 minutes

**URL:** <https://forum.ansible.com/t/help-needed-please-awx-isolated-node-not-registering-automatically-and-dropping-after-30-minutes/36598>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [May 5, 2022, 10:48am UTC](https://forum.ansible.com/t/help-needed-please-awx-isolated-node-not-registering-automatically-and-dropping-after-30-minutes/36598 "2022-05-05T10:48:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rhcalalo\_e](https://avatars.discourse-cdn.com/v4/letter/r/47e85d/32.png) [@rhcalalo\_e](https://forum.ansible.com/u/rhcalalo_e)\
**Post date:** [May 5, 2022, 10:48am UTC](https://forum.ansible.com/t/help-needed-please-awx-isolated-node-not-registering-automatically-and-dropping-after-30-minutes/36598/1 "2022-05-05T10:48:43Z")

</div>

Hi,

Good day. Hope this email finds you well.

I was running AWX 15.0.1 and I was trying to add an isolated node using the commands below:

# awx-manage provision\_instance --hostname --is-isolated

# awx-manage register\_queue --queuename restricted --hostname --controller tower

# awx-manage generate\_isolated\_key

then add this key to isolated node awx account /home/awx/.ssh/authorized\_keys

awx-manage list\_instances out will show the isolated node and group but the isolated node was unavailable, it was fixed by manually re-enabling the node in GUI however it dropped again after 30 minutes. I also noticed that isolated node heartbeat is not being check

Please advise if anyone has encountered the same and how to fix this issue.

Thanks a lot

---

<div class="post-metadata">

**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\
**Post date:** [May 11, 2022, 8:03pm UTC](https://forum.ansible.com/t/help-needed-please-awx-isolated-node-not-registering-automatically-and-dropping-after-30-minutes/36598/2 "2022-05-11T20:03:38Z")

</div>

Hi,

The heartbeat is probably running against this instance and failing, and after 30 minutes is being marked as lost. During the 30 minutes that the node is “available”, are you able to schedule and run jobs against that isolated instance? Do you see anything in the logs about the heartbeat check failing?

Seth