| Previous | Next |
| PEER_E_UNSUPPORTED_VERSION | PEER_E_GROUP_IN_USE |
PEER_E_GROUP_NOT_READY
Which peer contract was rejected
PEER_E_GROUP_NOT_READY — HRESULT 0x80632091 means that the operation requires an online group connection, but the local member has only opened/joined the group or has become disconnected. The relevant API boundary includes PeerGroupOpen/Join, PeerGroupConnect, PeerGroupGetStatus and group events.
Minimum diagnostic packet
| Item | Evidence |
|---|---|
| Raw input | Preserve PeerGroupGetStatus, connect events, member/neighbor counts, PNRP result, local group handle and the operation attempted before online state. |
| 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 connected group status, run the operation, then compare with the same call immediately after PeerGroupOpen.
Why the comparison code is different
PEER_E_NO_MEMBERS_FOUND differs because group-not-ready is local lifecycle state; no-members-found is a completed connection search with no active members.
Recommended change
Separate local database-open state from online group state and queue network-dependent actions until connection is confirmed.
Technical references
Looking for a different code? Search another status or error code.