PermissionProfileNotApplied
A required session-start permission-profile selection the client could not
prove applied: the start
result carried no permissionState, and the session/read read-back
served a different profile — or none at all. Never a silent default: the
session stays open and the caller decides (set/retry or close) via
sessionId, with no auto-close and no auto-set.
Properties
Section titled “Properties”| Property | Type | Stability | Presence | Description |
|---|---|---|---|---|
requested |
string |
required | The profile id the caller required. | |
served |
string | null |
required | The committed profile id the read-back served, or null when unknown. | |
sessionId |
string |
required | The open session, so the caller can set, retry, or close it. |
Methods
Section titled “Methods”| Method | Signature | Stability | Description |
|---|---|---|---|
constructor |
new PermissionProfileNotApplied(requested: string, served: string | null, sessionId: string) |
Source
clients/sdk-ts/src/errors.ts:81
{ "kind": "Class", "canonicalPath": "PermissionProfileNotApplied"}