| Previous | Next |
| WER_S_REPORT_UPLOADED | WER_S_DISABLED |
WER_S_REPORT_QUEUED
WER report was queued for later processing
WER_S_REPORT_QUEUED is HRESULT 1769474 (0x001B0002) from winerror.h. The documented description is “Report was queued.” In the Windows Error Reporting collection, queue, upload, archive, assertion, or debugging workflow, the value reports a nonfailure state that must not be collapsed into plain S_OK.
Telemetry and tests should retain this result because its operational meaning differs from S_OK.
Where the status is encountered
- WerReportSubmit and WER store processing; capture the exact API, object, and phase because the same numeric success severity does not define the state by itself.
- Crash, hang, assertion, and application-failure reporting;
- Enterprise policy controlling WER queue, archive, upload, debugger, and throttling;
What must be true before accepting it
Verify that the report is durably present in the WER queue and the application does not promise immediate delivery. The boundary determines whether the caller continues, waits, falls back, or ends the operation.
Difference from nearby results
Uploaded means transmission completed; queued means collection succeeded but delivery remains deferred.
Precise classification of it selects the correct wait, stop, retry, cleanup, or disclosure path.
Correct handling and recovery
Release application-owned temporary data only after queue persistence is confirmed, and let WER handle later upload according to policy and connectivity.
Practical scenario
A laptop is offline when a report is submitted. WER queues it, and the application records deferred delivery rather than retrying on every launch.
References
Looking for a different code? Search another status or error code.