> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/rules/common-rule-features/rule-settings/rule-state.md).
# Rule Status
## The two rule statuses
Every Rule has two status options: `Published` and `Pending`. The status can be set on each version of the rule independently.
**Initial Status:**
* **Newly created rules:** All rules are created in `Published` status by default
* **Imported rules:** The status is determined by the value defined in the imported rule data
* **New versions:** All newly created versions start in `Pending` status
### Published status
Rule in Published status is ready for production and is available via [Solver API](/doc/api/rule-solver-api/rule-solver-api-1.md).
#### Examples:
rules in Published status
### Pending status
Some rules or versions of rules are not yet ready for production. For example, because the rule is still in development. Such a rule has a Pending status and it cannot be accessed using [Solver API](/doc/api/rule-solver-api/rule-solver-api-1.md). When trying to solve such a rule, [Solver API](/doc/api/rule-solver-api/rule-solver-api-1.md) returns the following HTTP request error:
```javascript
400 Bad Request
{
"error": {
"message": "Rule state is not published"
}
}
```
{% hint style="success" %}
For the purpose of testing your rules and their versions that are not yet in production, you can execute rules in Pending status by using the **Debug** in [Test Bench](/doc/rules/common-rule-features/test-bench.md) feature to solve the rule directly within the platform.
{% endhint %}
#### Example:
rules in Pending status
### How to change the rule status
The status can be changed in rule settings by clicking the **Status toggle**. The rule **must be saved** to apply the status change.
switched to Pending
switched to Published
---
# 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.decisionrules.io/doc/rules/common-rule-features/rule-settings/rule-state.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.
