| Previous | Next |
| PEER_E_GRAPH_NOT_READY | PEER_E_GRAPH_IN_USE |
PEER_E_GRAPH_SHUTTING_DOWN
Which peer contract was rejected
PEER_E_GRAPH_SHUTTING_DOWN — HRESULT 0x80630014 means that graph teardown has started and the infrastructure no longer accepts new graph operations. The relevant API boundary includes PeerGraphClose, callback dispatch and application shutdown coordination.
Minimum diagnostic packet
| Item | Evidence |
|---|---|
| Raw input | Preserve shutdown initiator, outstanding callbacks, worker threads, open enumerations, direct connections and timestamps for close versus the rejected call. |
| 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
Block new work before initiating close, drain callbacks, and compare with a test that intentionally races one operation against graph teardown.
Why the comparison code is different
PEER_E_INVALID_GRAPH differs because after teardown completes the handle may become invalid; this code specifically identifies the in-progress shutdown interval.
Recommended change
Serialize shutdown with application work queues and release graph-dependent objects before invalidating the graph handle.
Technical references
Looking for a different code? Search another status or error code.