Maintenance Events
Focus
Focus
Prisma Browser

Maintenance Events

Table of Contents

Maintenance Events

Maintenance events indicate browser lifecycle issues such as unexpected closures, startup failures, and authentication errors.
Maintenance events appear under the Access category in the Events screen but represent system health and availability concerns rather than user-initiated access activity.
The authenticationFailure event is also included here because it typically indicates a system or configuration issue rather than a deliberate user action.

Event Types

Event TypeUI NameDescription
browserClosureBrowser closureThe Prisma Browser was closed (normally or unexpectedly)
browserStartupFailureBrowser startup failureThe Prisma Browser failed to start properly
authenticationFailureAuthentication failureAn authentication flow failed (SSO errors, MFA failures, token issues)

Context Fields

FieldUI LabelDescription
maintenance.issueReasonIssue reasonThe specific reason for the failure or closure
maintenance.authenticatedAuthenticatedWhether the event was sent via the authenticated pipeline (true) or the unauthenticated public API (false)

Issue Reasons — Internal Errors

ReasonDescription
Internal errorAn unspecified internal error occurred
Out of memoryThe browser ran out of memory
CrashThe browser process crashed
Killed externallyThe browser process was terminated by an external process
Binary corruptedThe browser binary failed integrity verification

Issue Reasons — Extension Issues

ReasonDescription
Extension not foundThe Prisma Browser Extension is not installed
Extension load failedThe extension failed to load
Extension pending installThe extension is pending installation
Extension not readyThe extension is installed but not ready
Extension init timeoutThe extension initialization timed out
Extension not runningThe extension is not currently running
Extension errorThe extension encountered an error

Issue Reasons — Authentication / Server Issues

ReasonDescription
Server unreachableThe management server could not be reached
Auth service rejectedAuthentication was rejected by the server
SSO flow failedThe SSO authentication flow failed
Auth token invalidThe authentication token is invalid or expired

Issue Reasons — Configuration Issues

ReasonDescription
Policy load failedThe policy configuration failed to load
Tenant removedThe tenant was removed from the system
Tenant not foundThe tenant could not be found
Profile bind failedThe browser profile binding failed
Profile already boundThe profile is already bound to another device

Issue Reasons — Administrative

ReasonDescription
TamperingBrowser closure triggered by tampering detection
Admin actionBrowser closure initiated by administrator action
Update requiredThe browser requires a mandatory update
Maintenance events with authenticated: false are sent through a public API path because the browser was unable to establish an authenticated session. These events may have limited device and user context.

Examples

Browser Startup Failure — Extension Not Found
FieldValue
TypeBrowser startup failure
CategoryAccess
Time2026-07-06 07:00:15 UTC
Userjohn.smith@acme.com
Issue reasonExtension not found
AuthenticatedYes
DeviceACME-LAPTOP-042
OSWindows 11
Browser version126.0.6478.127
Browser Startup Failure — Server Unreachable (Unauthenticated)
FieldValue
TypeBrowser startup failure
CategoryAccess
Time2026-07-06 08:30:00 UTC
User(limited — unauthenticated event)
Issue reasonServer unreachable
AuthenticatedNo
DeviceUNKNOWN-DEVICE
OSmacOS 14.5
Browser Closure — Crash
FieldValue
TypeBrowser closure
CategoryAccess
Time2026-07-06 16:45:33 UTC
Usersarah.kim@acme.com
Issue reasonCrash
AuthenticatedYes
DeviceACME-MACBOOK-089
OSmacOS 14.5
Browser version126.0.6478.127
Browser Closure — Admin Action
FieldValue
TypeBrowser closure
CategoryAccess
Time2026-07-06 14:00:00 UTC
Usermike.chen@acme.com
Issue reasonAdmin action
AuthenticatedYes
DeviceACME-DESKTOP-117
OSWindows 10