e.state.conflict.registry.exists.f¶
A registry with that identifier is already in this lockbox, and a second one would silently become the first.
Retrying the same thing changes nothing.
What a response says¶
The registry {regid} is already here, and the nonce and timestamp you named derive that same identifier.
The placeholders are filled from regid, which travel positionally in the args member of the response.
What to do¶
keripy treats a repeated registry inception as idempotent and returns without complaining (`regeventing.py:562`), which is right for a replayed event and wrong for a second registry — the caller would come away holding the first one believing it was new. Leave the nonce and the timestamp unset and heti mints fresh ones.
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.exists..
Declared in heti.