| Previous | Next |
| PSINK_S_LARGE_WORD | CI_S_END_OF_ENUMERATION |
CI_S_WORKID_DELETED
Indexing work ID refers to a deleted item
CI_S_WORKID_DELETED is HRESULT 268302 (0x0004180E) from Indexing Service. AllStat describes it as “The workid is deleted.” 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 the workid is deleted. The high-level request can be considered complete after it only when its documented postcondition has been checked.
Where the status is encountered
- Legacy Indexing Service catalog processing; log the exact method and object state instead of interpreting the constant outside that contract.
- IFilter text and property extraction; log the exact method and object state instead of interpreting the constant outside that contract.
- 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.
What must be true before accepting it
Verify that the deleted work ID is removed from pending operations and cannot be reused for a different document generation. The verification prevents it from being promoted to broader success than the producing API promised.
The component may have changed durable or in-memory state before returning it; inspect that state first.
Evidence and telemetry
- preserve work ID and catalog generation.
- preserve source URL or path.
- preserve delete timestamp.
- preserve pending operation type.
- preserve replacement item identity if recreated.
Also record ci_s_workid_deleted_operation, ci_s_workid_deleted_state_before, ci_s_workid_deleted_state_after, UTC time, process and thread identifiers, component version, and a correlation ID. Protect user data in logs and keep only the identifiers required to reproduce component state.
Correct handling and recovery
Discard stale work for that ID, reconcile the catalog delete, and obtain a new identity if the source item is recreated.
Retry it only when a documented input or state has changed. Retry policy must follow the owning state machine rather than a generic transient-error loop.
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 nearby-status comparison controls whether outputs are usable and whether more work is expected.
Practical scenario
A delayed property update targets a document deleted earlier. The service drops the update, confirms the tombstone, and does not apply it to a later file that reuses the path.
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.
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.