agent's usage export parser returned empty seat counts, audit failed

Not specified by the original author.

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

(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

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

Thread query: license agent failed to parse Atlassian org audit log, seat export empty

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.

Not specified by the original author.

TL;DR

Empty output with no error means the parser silently dropped everything. Check that the raw export is non-empty, validate the parser's row count against it, find which filter dropped the rows, usually an over-strict status filter, and fix it.

agent's usage export parser returned empty seat counts, audit failed

Use this when

• A usage parser returns zero counts with no error.
• The raw export file is non-empty.
• The audit reports zero with false confidence.

Not for this skill when

• The export is genuinely empty. That is a data problem.
• The parser errors. Read the error.
• The counts are wrong but non-zero. That is a logic problem.

Steps

1. Check the raw export is non-empty. Verify: the file has data.
2. Validate the parser's row count against the raw line count. Verify: you see the drop.
3. Inspect which filter dropped the rows. Verify: the culprit filter is named.
4. Fix the filter; status values and date formats are the usual suspects. Verify: rows survive.
5. Re-run the parse. Verify: counts are non-empty and sane.

Variant phrasings

parser returned empty

The state-first phrasing.

seat counts zero

The symptom-first search.

empty audit results

The generic phrasing.

Compatibility: Any usage export parser in agent code.

Why it happens

Parsers that filter aggressively return empty instead of erroring. The audit then reports zero with false confidence, which is worse than failing loudly.

Edge cases / pitfalls

• The export genuinely having zero rows for the filter; distinguish from parser error by checking the raw file.
• Status values the vendor renamed; the filter matches nothing.
• Date-format mismatches silently excluding every row.
• The fix needing a loud failure on empty results going forward, so this never recurs silently.

Provenance

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

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

Thread query: agent's usage export parser returned empty seat counts, audit failed

TL;DR: Empty output with no error means the parser silently dropped everything. Check that the raw export is non-empty, validate the parser's row count against it, find which filter dropped the rows, usually an over-strict status filter, and fix it.

Not specified by the original author.

TL;DR

Fix this in Permission audit agent by acting on the exact symptom first: use the brand article export or API listing when scraping returns empty, verify the article count per brand against the admin total, and refuse to report a brand as clear based on an empty scrape. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Scraper failed on the brand article listing and returned empty results for auditing permissions

Use this when

• Work in Permission audit agent shows this exact symptom: Scraper failed on the brand article listing and returned empty results for auditing permissions.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Permission audit agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: use the brand article export or API listing when scraping returns empty, verify the article count per brand against the admin total, and refuse to report a brand as clear based on an empty scrape. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Permission audit agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Scraper failed on the brand article listing and returned empty results for auditing permissions

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - scraper failed on brand article listing returning empty results for auditing permissions error scraping failure

The how to phrasing for the same problem in Permission audit agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Permission audit agent troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Brand listings render with scripts after the initial page load, so a plain scrape collected no articles and an audit based on it would have passed every permission unchecked.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Permission audit agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

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

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

Thread query: scraper failed on brand article listing returning empty results for auditing permissions error scraping failure

TL;DR: Fix this in Permission audit agent by acting on the exact symptom first: use the brand article export or API listing when scraping returns empty, verify the article count per brand against the admin total, and refuse to report a brand as clear based on an empty scrape. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.