Skip to main content
GET
List error flavours

Authorizations

Authorization
string
header
required

Use an Observe API key from the management console. The key selects the project and must grant the permission listed on the operation. Keep this key on your server.

Response

All error flavours of the project, sorted by first-seen (descending).

Maximum array length: 100000
id
string
required

Error flavour ID (format erf-<number>).

subFlowType
string
required

Subflow type the flavour belongs to (e.g. passkey-login).

stepName
string
required

Step the error occurred on ("" for subflow-level errors).

name
string
required

Raw error name from the tracking event (e.g. NotAllowedError; "" for code-only and step-incomplete flavours).

message
string
required

Raw error message from the tracking event ("" for code-only and step-incomplete flavours).

code
string
required

Raw error code from the tracking event ("" when the error carried name/message instead).

uiPatterns
string
required

Canonical comma-joined set of UI patterns observed during the error ("" for none).

specType
string
required

Resolved subflow spec type the error occurred under ("" when the subflow has none).

trigger
enum<string>
required

What produced the flavour - an explicit error event, a must-complete step that ended neither finished nor errored, a step the subflow had to reach that never appeared at all, or a subflow with interaction evidence but no step or error event at all.

Available options:
step-error,
step-incomplete,
step-missing,
no-followup
durationBucket
enum<string>
required

Bucketed step-start to error latency (na when not measurable).

Available options:
0,
le100,
le2000,
le30000,
gt30000,
na
firstSeenMs
integer<int64>
required

Timestamp of the occurrence that minted this flavour, in milliseconds since epoch.

errorID
string

ID of the error this flavour is mapped to (format err-<number>); absent while unmapped.

assignSource
enum<string>

Who made the current error assignment - a human in the Management Console (manual), a deterministic knowledge-base rule (kb), or AI/agent judgment (agent). Absent while unmapped and on assignments made before provenance existed.

Available options:
manual,
kb,
agent
assignReason
string

Human-readable explanation of why this flavour belongs to its error. Absent under the same conditions as assignSource.