Skip to main content
IronBee buffers session events in a file-backed queue before sending them to the Collector. This happens automatically in the background and you rarely need to touch it. These commands are for diagnosing or recovering delivery when something stalls (e.g. you were offline and events piled up).

​
Check queue status

Show queued job counts per session across the project:

​
Drain pending jobs

Process queued jobs synchronously, sending them to the Collector now instead of waiting for the background flush:

​
Dead-letter queue

Jobs whose failures are permanent land in a dead-letter queue so they don’t block healthy traffic. Transient failures (network errors, 429, 5xx) are retried on the next drain; anything else — an auth rejection (401/403, e.g. an expired credential) or any other 4xx — is dead-lettered on the first attempt rather than retried pointlessly. Events dead-lettered under a bad credential won’t auto-deliver later: fix the credential, then re-queue them with dead-letter retry (dead-letter stats shows the auth:* category). Inspect and recover them:

​
Purge

Destructive cleanup of queue state. Use with care:
purge permanently drops queued data. --snapshots discards events that were never sent. Reach for drain first if you want to deliver pending events rather than throw them away.
All of these commands are available interactively in the TUI Queue area.

​
What’s next?

Runtime files

The queue/ directory and everything else IronBee writes per session.

Inspecting sessions

Check verdict status and validate sessions from the terminal.