# Project logging standards

<table><thead><tr><th width="138">Check ID</th><th>DEV_0005</th></tr></thead><tbody><tr><td>Category</td><td>Standards</td></tr><tr><td>Summary</td><td>This check will ensure that the logging that you have added to your project meets your standards.</td></tr><tr><td>Options</td><td>See the table below for all available options. </td></tr><tr><td>Pass</td><td>The element matches your standards.</td></tr><tr><td>Fail</td><td>The element does not match your standards.</td></tr></tbody></table>

### Project Logging Standards <a href="#id-79.mxom_checks.policycheck.groupbox1_hee_243_header" id="id-79.mxom_checks.policycheck.groupbox1_hee_243_header"></a>

<table><thead><tr><th width="182">Option Name</th><th>Details</th></tr></thead><tbody><tr><td>Log Nodes</td><td>If TRUE, log nodes should not use hardcoded values (use constants instead). Default: TRUE</td></tr><tr><td>Custom Error Handling</td><td>If TRUE, the first action in a custom error handler should be a log action. Default: TRUE</td></tr><tr><td>Decisions</td><td>If TRUE, decisions should always have a caption. Default: TRUE</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bluestorm.io/checks/development/dev_0005.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.