| Previous | Next |
| SEARCH_S_NOMOREHITS | FILTER_S_LAST_TEXT |
FILTER_W_MONIKER_CLIPPED
Filter moniker covers only part of the region
FILTER_W_MONIKER_CLIPPED is HRESULT 268036 (0x00041704) from Indexing Service. AllStat describes it as “Moniker doesn't cover entire region.” The severity bit indicates a nonfailure result, but the value carries a specific condition that must not be collapsed into plain S_OK.
In the legacy Indexing Service or IFilter pipeline, this result means that moniker doesn't cover entire region. Consumers of it must decide from the API contract whether to stop, wait, continue, or expose a reduced outcome.
What must be true before accepting it
Verify that the caller knows which region the moniker represents and does not attribute extracted content to the whole document. Checking the boundary keeps this result from hiding stale data, pending work, or a deliberately reduced result.
Do not compensate for it until the caller knows which sub-operations actually occurred.
Where the status is encountered
- This result can be returned during legacy Indexing Service catalog processing; log the exact method and object state instead of interpreting the constant outside that contract.
- This result can be returned during IFilter text and property extraction; log the exact method and object state instead of interpreting the constant outside that contract.
- It can be returned during search enumeration, scan scheduling, or catalog administration; log the exact method and object state instead of interpreting the constant outside that contract.
Because it is informational, a language binding may expose it as success and hide the symbolic distinction. Keep the original HRESULT available until the code-specific branch has run.
Evidence and telemetry
- preserve moniker display name.
- preserve region start and extent.
- preserve parent document identity.
- preserve chunk source IDs.
- preserve offset mapping between region and document.
Also record filter_w_moniker_clipped_operation, filter_w_moniker_clipped_state_before, filter_w_moniker_clipped_state_after, UTC time, process and thread identifiers, component version, and a correlation ID. A diagnostic bundle for it should preserve correlation fields without copying tokens, keys, or private media.
Correct handling and recovery
Record the region boundaries and moniker, then either process the uncovered regions separately or mark the extraction as partial. Avoid generating document-wide offsets from clipped input.
Retry it only when a documented input or state has changed. Continuation after it may be appropriate, but an identical restart is not automatically recovery.
Practical scenario
A compound-document filter receives a moniker for one embedded object rather than the entire file. The indexer tags extracted text with the embedded region and schedules the remaining regions independently.
A regression test should reproduce it, assert the relevant outputs and state, then change only the decisive condition and verify the expected neighboring result or ordinary completion.
Difference from nearby results
It must be distinguished from ordinary S_OK and from failure-severity values in the same API family; its documented state changes control the next action.
The practical value of distinguishing it is choosing the right wait, stop, retry, or user-notification behavior.
References
- Microsoft: Filter interface values — official Microsoft material used to interpret it.
- Microsoft: About Indexing Service filters
- Microsoft: Using custom filters
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.