| Previous | Next |
| PEER_E_DUPLICATE_GRAPH | PEER_E_GRAPH_SHUTTING_DOWN |
PEER_E_GRAPH_NOT_READY
Which peer contract was rejected
PEER_E_GRAPH_NOT_READY — HRESULT 0x80630013 means that the requested operation requires a connected graph, but the local node has not reached connected state. The relevant API boundary includes PeerGraphConnect, PeerGraphGetStatus, graph event registration and the failed graph operation.
Minimum diagnostic packet
| Item | Evidence |
|---|---|
| Raw input | Preserve PeerGraphGetStatus result, connect and listen events, neighbor count, PNRP resolution outcome, callback sequence and the operation attempted too early. |
| Owning context | Record the Windows user, process integrity, graph or group handle, database path and selected cloud. |
| Previous success | Save the last successful create, open, enumerate, parse, register or sign-in result that produced the object. |
| Result order | Retain the first HRESULT so cleanup failures do not replace the code that rejected the request. |
Focused reproduction
Wait for the graph status/event that proves connectivity before the operation, and compare with the same call immediately after open.
Why the comparison code is different
PEER_E_GRAPH_SHUTTING_DOWN differs because not-ready is a pre-connect or disconnected state; shutting-down is a terminal transition after teardown has begun.
Recommended change
Gate connectivity-dependent work on graph status and events rather than on successful open alone.
Technical references
Looking for a different code? Search another status or error code.