:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Python ab-testingai-analyticsanalyticscdpdata-warehouseexperimentsfeature-flagsjavascriptproduct-analyticspythonreactsession-replaysurveystypescriptweb-analytics
/**
* An expected request failure: the backend said no (4xx/5xx), the network was unavailable,
* or the response body was unusable. These are normal outcomes of talking to the API from
* a customer's page - they must never be reported to error tracking.
*
* `toolbarApi` itself never throws (it returns a `ToolbarApiResult` union). Logics that
* need a kea `*Failure` action to fire (to drive UI state or a toast) convert a failed
* result into a throw - that throw must be a `ToolbarRequestError`, so the global kea
* loader handler (see `index.tsx`) can log it without capturing an exception. Throwing a
* plain `Error` from a loader is reserved for genuine bugs, which SHOULD be captured.
*/
export class ToolbarRequestError extends Error {
/** HTTP status of the failed response, or 0 for a network-level failure. */
status: number
constructor(message: string, status: number = 0) {
super(message)
this.name = 'ToolbarRequestError'
this.status = status
}
}
/**
* Preferred over a bare `instanceof` check: on customer pages the error can cross
* realm/bundle boundaries (duplicate toolbar bundles, page wrappers around fetch/DOM
* APIs), where class identity is lost. Fall back to the `name` tag so a tagged request
* failure is never misclassified as a genuine bug.
*/
export function isToolbarRequestError(error: unknown): boolean {
if (error instanceof ToolbarRequestError) {
return true
}
return typeof error === 'object' && error !== null && (error as { name?: unknown }).name === 'ToolbarRequestError'
}