e.state.conflict.registry.gid.f¶
That registry event belongs to a different registry than the proposal names, so I won't act on it.
Retrying the same thing changes nothing.
What a response says¶
The proposal names the registry {named} and the event it carries belongs to {found}. Acting on it would grow a chain this ceremony was never about.
The placeholders are filled from named, found, which travel positionally in the args member of the response.
What to do¶
A member in more than one group holds more than one registry, and an artifact naming the wrong one is well-formed and correctly signed — only its subject is wrong.
Where it sits¶
| Sorter | e — Error. The problem clearly defeats someone's intentions. |
| Obstacle | e.state. — The condition of the target |
| Disposition | f — Final. Retrying the same thing changes nothing. |
A handler can match this code exactly, or by any prefix above it: e.state., e.state.conflict., e.state.conflict.registry., e.state.conflict.registry.gid..
Declared in heti.