# BRM Queue Report
A full-page queue manager for the BRM background processing queue. Lists every queue record with status filters, lets staff retry failed records, edit payloads before retrying, and trigger the queue processor on demand.
This is the heavyweight queue view, intended for administrators who need to see and act on the whole queue. For an at-a-glance widget, use **BRM Queue Widget** instead.
## Available in
* Reports modules
* Page modules
## When to use
* Operations dashboards where staff monitor and clear the BRM queue.
* Admin pages where someone needs to retry stuck transactions or fix a malformed payload before re-running it.
* Troubleshooting pages where you need to see exactly what went wrong with a specific queue record.
## Settings
The block opens a configuration modal:
| Setting | Description |
| ------------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Title** | Block heading. Default: *BRM Queue Report*. |
| **Refresh Interval** | Seconds between automatic refreshes. 0 = no auto-refresh (manual only). Default: 0. |
| **Page Size** | Records per page. Default: 50. |
| **Show Export** | Show the *Export* button (downloads the current view as CSV). Default: Yes. |
| **Show Retry Button** | Show the per-row *Retry* action. Default: Yes. |
| **Show Payload Editor** | Allow editing a record's payload before retry. Default: Yes. |
| **Show Status Filter** | Show the status-filter dropdown above the table. Default: Yes. |
| **Default Status Filter** | Status filter applied on load — *errors* (statuses 4 + 5), *all*, or a specific status. Default: *errors*. |
## How it works
1. Reads the BRM queue records via NetSuite SuiteQL — paginated by Page Size.
2. Renders them in a table with columns for record type, status, payload preview, error message, and timestamps.
3. **Retry** re-queues a single record. **Edit Payload** opens an inline editor; saving the edit also re-queues it.
4. **Trigger Processor** runs the BRM queue processor immediately so retried records are picked up without waiting.
5. Auto-refreshes if Refresh Interval is set, otherwise refreshes only on manual action.
## Examples
**Queue ops dashboard.** A Reports module with BRM Queue Report at the top, default status filter *errors*, refresh interval 30 seconds. Operations staff land on the page and see only failures, auto-refreshing.
**Read-only audit page.** Hide *Show Retry Button* and *Show Payload Editor*. Show all statuses. Useful for managers who want visibility without write access.
## Common issues
* **No records appear** — the BRM queue may genuinely be empty, or the user's NetSuite role may not have access to the queue record. Check role permissions.
* **Retries don't process** — the queue processor isn't running. Click *Trigger Processor* or contact your NetSuite administrator about the scheduled script.
* **Edit Payload changes don't save** — verify the user has edit permission on the queue record. Read-only roles will see the editor but not be able to save.
## Related
---
# 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.in8sync.com/client-admin-guide/active-workflows/getting-started/report-components/brm-queue-report.md?ask=
```
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.