> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/marketplace/requests/set-request-to-processing.md).

# Set querying requests to processing

Set your querying request to processing.

When you update your request, for example, by attaching documents, it's important to change the request status to **Processing** and send the request back to the vendor. This action informs the vendor that you've replied to their query, and the request is now ready for their review. 

Before changing the status of your request, note the following points:

* You can change the status of your request to **Processing** only if the current status is **Querying**. If the request is already in the **Processing** or **Completed** state, the option to change the status is unavailable. 
* Only change the status of your request to **Processing** once you've provided all the information and the request is ready for the vendor's review.

## Setting a querying request to processing

To change the status of your request:

1. On the **Requests** page, select the required request. The request details page is displayed.
2. Make changes as necessary and then click **Process**. 
3. In the **Process request** dialog, add your comments, and then select **Process**. 

<figure><img src="https://content.gitbook.com/content/Z5DNbniz33mXCZoO62Rm/blobs/AJs0a21gNxblGa6er55F/image.png" alt="" width="563"><figcaption><p>Process request dialog</p></figcaption></figure>

The status of your request changes from **Querying** to **Processing**. If you added comments in the **Process request** dialog, your comments are displayed and visible to everyone on the **Activity** tab.&#x20;


---

# 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.platform.softwareone.com/modules-and-features/marketplace/requests/set-request-to-processing.md?ask=<question>&goal=<user_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.