> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/general-render-network/what-role-am-i/how-to-get-started-1/running-multiple-programs-or-tasks.md).
# Running Multiple Programs or Tasks
Getting the most out of the Render Network client
If you have a lot of GPU intensive background tasks running while processing renders on the Render Network, it may lead to job failures that will hurt your reputation score.
As a result, we recommend connecting your node to the Render Network only when you are able to commit most of your GPU, RAM, and CPU resources to the Render Network. \
Mining multiple networks simultaneously or running background programs will lead to excessive failures and **potential quarantining of your node.**
{% hint style="warning" %}
**Any nodes that are *****inactive***** for *****3 months or more***** will be considered "****expired****" and *****removed from the Network*****, and expired operators will *****need to reapply***** to the waitlist in order to have their nodes considered for re-entry onto the Network. Please see subsection 1.8 of the Node Operator (FKA "Miner") Terms of Agreement for justification, whereby the Network can revoke operator access at any time.**
{% endhint %}
---
# 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://know.rendernetwork.com/general-render-network/what-role-am-i/how-to-get-started-1/running-multiple-programs-or-tasks.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.