> For the complete documentation index, see [llms.txt](https://docs.nusa.nissology.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nusa.nissology.ai/hosting/pausing-rentals.md). # Pausing rentals Your machine is listed while Nusa Node is running and online. When you need your computer back, **pause** rentals instead of quitting Nusa Node: a rental under way finishes first, and pausing never lowers your reliability score. ## Pause rentals From your machine's page, choose **Pause rentals**, and select a duration: * **1 hour** * **4 hours** (chosen for you on the machine's page unless you pick another) * **24 hours** * **until you resume** If the machine is rented, the rental carries on to its end and no new one starts. When the time you chose runs out, your machine is listed again by itself. To come back sooner, resume it. * **A restart doesn't undo it.** Your machine stays paused until you resume it or the time runs out. * **You can pause or resume while your machine is offline.** * **"Until you resume" sends a reminder.** Nusa emails you after 3 days. * **You can't pause while the benchmark is running.** ## Quitting Nusa Node during a rental If you quit the desktop app while your machine is rented, it warns you first: quitting ends the rental, the renter is refunded, you aren't paid for it, and it lowers your reliability score. The warning offers to pause rentals instead. Here, 24 hours is chosen for you unless you pick another, since you may be switching the computer off. The rental finishes, and the app quits by itself once it has. ## Turning your computer off Unplugging or switching off your computer isn't pausing. To Nusa, the machine has gone offline. * **A short drop doesn't end anything.** If the connection comes back shortly, the rental carries on and no email is sent. Being disconnected while rented still lowers the reliability score. * **If it doesn't come back, Nusa confirms it's offline.** That's about the machine, whether or not anyone is renting it. * **If someone was renting it, that rental is interrupted:** it ends early, the renter is refunded, you aren't paid for it for now, and it lowers your reliability score unless a review finds your machine wasn't at fault. See [Refunds](file:///6919936/renting/refunds.md#for-hosts). ### The emails you get Being offline and having a rental interrupted each have their own email: * **A rental was interrupted:** sent at once, with how to ask for a review. * **Your machine is offline:** sent once Nusa has confirmed it's offline and it has stayed offline for 30 minutes, whether or not it was rented. You get it once each time the machine goes offline, and not while it's paused. You may get one of them or both. ## Removing a machine When you retire, sell, or repurpose a machine, remove it on the machine's page. * **A machine that's rented can't be removed** until the rental ends. Pause rentals so no new one starts meanwhile. * **Your history stays.** Its past rentals and earnings stay in your Earnings. --- # 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://docs.nusa.nissology.ai/hosting/pausing-rentals.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.