> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/s2gw-installation-manual/troubleshooting/xml_examples/s2gw-no-answer-from-a-node.md). # S2GW No answer from a node The message from S2GW if it did not receive any answer from a node over radio. This happens if the node is powered off, out of range or have incorrect radio net or ID settings. This message is sent in a separate post. The node is removed from the list of nodes to be polled. The node will be polled again after the configuration refresh from B3 which by default happens every 15 minutes or when configuration in B3 is changed. If it will be online, the S2GW will start polling it as defined. ```xml 22 2 9304 1 No communication with node ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.boomerang3.com/s2gw-installation-manual/troubleshooting/xml_examples/s2gw-no-answer-from-a-node.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.