> For the complete documentation index, see [llms.txt](https://manual.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.firstresonance.io/plans-and-autoplan/manualy-changing-autoplan-status.md).

# Manualy Changing Autoplan Status

If Autoplan gets stuck in an "IN PROGRESS" state, you can manually update the job status to unblock future Autoplan runs.

To avoid this issue, we recommend running Autoplan with a reasonable scope. Planning for an entire year’s worth of product can put excessive strain on the system. Instead, plan for just this quarter’s demand or a smaller subset.

To change the status of the Autoplan job you can follow the bellow sequence of queries:

1\. Find the etag of the Autoplan job in question. We'll then use this etag to help us update the job status.

```
{
  mrpJob(id: <INSERT ID>) {
    _etag
    id
  }
}
```

2. Run the following query and input variables in GraphQL to update the status.

```
mutation updateMRP($input:UpdateMRPJobInput!) {
  updateMrpJob(input:$input){
    mrpJob {
      id
    }    
  }
}

#INPUT VARIABLES TO BE PLACES IN QUERY VARIABLES SECTION
{
  "input": {
    "id": <INSERT ID>,
    "status": "<INSERT DESIRED STATUS, LIKELY "FAILED">",
    "etag":  "<INSERT ETAG FROM QUERY RESULTS IN STEP ONE>"
  }
}
```

Completing this sequence of queries in GraphQL will allow you to update the status of any Autoplan job should it be stuck "IN PROGRESS".


---

# 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://manual.firstresonance.io/plans-and-autoplan/manualy-changing-autoplan-status.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.