> For the complete documentation index, see [llms.txt](https://cfscribe.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cfscribe.ortusbooks.com/getting-started/appenders/screenabort.md).

# ScreenAbort

The ScreenAbort appender is designed to use with remote access tools such as a [Postman](https://www.postman.com/). Its main purpose is to return dump() output to the client so the error message can be viewed as if the user was viewing the call from a browser. 

**Configuration**

The ScreenAbort appender is active by default and can be used with no properties.

**Note**: This WILL abort processing the page and immediately return the call. See tips below for recommendations   

```
appenders : {
   "screenDump"  : { "class" : "scribe.models.screenDump" }
}
```

**Tips and Recommendations**

* Use in conjunction with an http header which is sent from your client. For example, create a header called "x\_DebugHeader and then in the [RuleDefinitions ](/getting-started/rules-and-rule-definitions.md)include `["headerTrueFalse":"x-DebugHeader"]`. This will check for the presence of the http header and route any errors accordingly. 
* Only use for `Fatal` or `Error` level logging. Otherwise every info comment will abort your flow. 
* When used in a series of apenders, put this last on the list otherwise the other appenders will not run. See below for example

**Example Configuration**

```
"ruleDefinitions" : [
    "headerTrueFalse:X-Import-Debug",
    "severity:severity"
],
rules : { 
    "true" : {
      "fatal" : [ "scribeConsole", "screenAbort" ],
      "error" : [ "scribeConsole", "screenAbort" ],
      "warn"  : [ "scribeConsole" ],
      "info"  : [ "scribeConsole" ],
      "debug" : [ "scribeConsole" ] 
    }
}
```


---

# 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 dynamically by asking a question.

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

```
GET https://cfscribe.ortusbooks.com/getting-started/appenders/screenabort.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.