Diagnose an action backlog or disk queue#

When to use this procedure#

Use for action cache, queue manager, disk queue, retry, and saturation events.

Applies to#

This procedure applies to EventReporter.

Prerequisites#

  • Use an account that can read the product configuration and Windows diagnostic state.

  • Replace angle-bracket placeholders with values from the affected system.

Safety#

  • Do not delete, rename, copy over, or manually edit active queue files.

  • Collect evidence before any support-directed recovery.

Configuration path#

Configuration Client > the service, rule, or action named on the Event ID page.

Procedure#

  1. Record queue depth, oldest item time, target action, directory, and whether depth is increasing.

    Expected result: The affected object and its effective settings are identified.

    If it fails: Return to the complete Event Log detail and configuration export before changing settings.

  2. Run the native Windows checks below from the affected product host.

    Get-ChildItem -LiteralPath '<QUEUE_DIRECTORY>' | Measure-Object -Property Length -Sum
Get-PSDrive -Name '<DRIVE_LETTER>' | Format-List Used,Free

    Expected result: Queue files are readable, space remains, the downstream cause is corrected, and depth decreases.

    If it fails: Diagnose the first downstream error; never edit or delete live queue files.

  3. Perform one uniquely identifiable product test through the same service, rule, or action.

    Expected result: The intended destination records the test exactly once.

    If it fails: Collect the first new product event and bounded debug output; do not change unrelated settings.

Verify the result#

Repeat the affected operation, confirm its positive output, and verify that queues, collection positions, or remote delivery continue normally.

Evidence to collect#

  • The complete Event Log entry and neighboring product events with timestamps.

  • The command output, relevant configuration export, and bounded debug log from the same interval.