## TL;DR
Verify the audit log API version and event types; an empty export means the parse matched nothing. The log format or endpoint changed under the parser.

## Error
```text
(seat export empty; audit log API returned data; parser matched zero events; no error text)
```

## Steps
1. Fetch a raw page of the audit log and inspect its shape: field names, event types, pagination. Expected: the actual format in hand.
2. Compare against the parser's expectations. Expected: the mismatch found (renamed fields, new event types, different pagination).
3. Update the parser to the current format, keying on stable identifiers. Expected: events parse.
4. Re-run the export. Expected: seat data present.

## When to use
- The seat export is empty but the API returns data
- Atlassian changed the audit log format or version
- The parser was written long ago

## When not to use
- The API returns nothing (an API or permission problem)
- The export has data but the counts are wrong (a counting problem)
- You need billing counts, not audit events (different source)

## Tool compatibility
Atlassian organization audit log API.

### Variant phrasings
### parse worked until last month
The format changed. Diff old versus new raw responses.

### parser matches some events but not seats
The seat-relevant event types changed names. Update the event list.

## Why it happens
Vendors evolve APIs without bumping the parsers that consume them. A silent format change turns a working parser into one that matches nothing.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_7sZLHTvuw5a4FE7a0SNlVw