e.input.format.oobi.data.f¶
That address serves a document, not an identifier, so there is no key state in it.
Retrying the same thing changes nothing.
What a response says¶
{oobi} answered with a schema whose SAID is {said}, the value its path names, so it is a data OOBI rather than an identifier's.
The placeholders are filled from oobi, said, which travel positionally in the args member of the response.
What to do¶
Learn the schema from it with resolve_schema (`schema learn` on screen). An identifier's OOBI may also name a role, as in /oobi/<aid>/witness, which removes the ambiguity (@9kvpvtr5).
Where it sits¶
| Sorter | e — Error. The problem clearly defeats someone's intentions. |
| Obstacle | e.input. — What you sent |
| Disposition | f — Final. Retrying the same thing changes nothing. |
A handler can match this code exactly, or by any prefix above it: e.input., e.input.format., e.input.format.oobi., e.input.format.oobi.data..
Declared in heti.