> ## Documentation Index
> Fetch the complete documentation index at: https://parser.xdr.ooo/llms.txt
> Use this file to discover all available pages before exploring further.

# Auto Parser: one event spans several lines

> Confirm where one full event ends when source text spans several lines.

# My log contains a multi-line error

**Situation:** You copy a Java application error that contains an exception title followed by many indented lines. Those lines might belong to **one event** instead of several.

## Fictional example

```text theme={null}
java.lang.IllegalArgumentException: invalid argument
    at example.Service.process(Service.java:42)
    at example.Main.main(Main.java:10)

java.lang.IllegalStateException: cannot continue
    at example.Worker.run(Worker.java:51)
    at example.Main.main(Main.java:12)

```

## Walkthrough

1. Paste the **complete text**, including the empty line between the two exceptions, into **Auto Parser → Add Logs**.
2. Click **Analyze Logs**. Look at the number of logical events reported. The example has **two exceptions**, not six separate events.
3. If the app offers **These look like Java error stack traces**, read the explanation and use **I Confirm Each Java Error Is Separated by a Blank Line** only when it matches the actual way records are separated at the source.
4. Continue to **Review Fields** and inspect the exception class, optional cause class and number of frames.
5. Review mapping, then use **Create Parser** only if that exact, reviewed multiline framing is supported.

## Expected review outcome

The complete stack trace stays together under one event. Parser Studio does not independently parse each indented line as another exception.

## Recovery path

If your source does not reliably separate complete exceptions by blank lines, **do not** select that confirmation just to force generation. Obtain the actual message boundary from the log source first.

<Note>
  You do not need to know the term "multiline framing" before pasting. You only need to confirm how **one complete error ends** when Parser Studio asks.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.