| Previous | Next |
| PEER_E_GROUPS_EXIST | PEER_E_DATABASE_ACCESSDENIED |
PEER_E_RECORD_NOT_FOUND
Which peer contract was rejected
PEER_E_RECORD_NOT_FOUND — HRESULT 0x80630301 means that the requested record ID is absent from the local graph or group record database at the time of lookup or update. The relevant API boundary includes PeerGraphGetRecord, PeerGroupGetRecord, update/delete calls and record event handling.
Peer records combine a typed record structure, optional searchable XML attributes, payload data, creator metadata and expiration. The local database may receive records in an order different from application dependencies.
Minimum diagnostic packet
| Item | Evidence |
|---|---|
| Raw input | Preserve record GUID, record type, creator ID, local database generation, expiration, delete events and whether synchronization has completed. |
Focused reproduction
Enumerate records of the expected type and immediately retrieve one returned ID, then compare with the stale requested ID.
Why the comparison code is different
PEER_E_DATABASE_NOT_PRESENT differs because record-not-found concerns one logical record inside an available database; database-not-present means the store itself is missing.
Recommended change
Refresh application indexes after record deletion/expiration and tolerate replication order rather than assuming a remote record is already local.
Technical references
Looking for a different code? Search another status or error code.