e.feature.unsupported.sedi-profile.f¶
That schema claims a SEDI profile I have not reviewed, so I cannot use its profile fields.
Retrying the same thing changes nothing.
What a response says¶
Schema {said} declares {profile} version {version}, but this verifier has no pin for that schema and version.
The placeholders are filled from said, profile, version, which travel positionally in the args member of the response.
What to do¶
Use a pinned SEDI schema, or add a reviewed revision to the verifier's allowlist.
Where it sits¶
| Sorter | e — Error. The problem clearly defeats someone's intentions. |
| Obstacle | e.feature. — The availability of a capability |
| Disposition | f — Final. Retrying the same thing changes nothing. |
A handler can match this code exactly, or by any prefix above it: e.feature., e.feature.unsupported., e.feature.unsupported.sedi-profile..
Declared in heti.