Skip to main content
All Docs
FeaturesmyProp (AgentOS People Portal)Updated April 3, 2026

Error Handling & Static Pages

Error Handling & Static Pages

Introduced in v0.1.2

myProp includes a set of purpose-built error pages and error boundaries to handle failure states gracefully. Rather than exposing raw error output or blank screens, the portal surfaces clear, user-friendly messages with navigation options that guide users back to a working state.


Error Pages

Company Not Found

Displayed when the portal is accessed with an agency identifier that does not match any known company in the AgentOS platform.

When it appears:

  • The subdomain or agency slug in the URL does not correspond to a registered agency.
  • The agency account is inactive or unreachable.

What the user sees:

  • A clear message explaining the agency could not be found.
  • A prompt to check the URL or contact their agency for the correct portal link.

500 Internal Server Error

Displayed when an unexpected server-side error occurs during a request.

When it appears:

  • An API call to AgentOS fails in an unrecoverable way.
  • A server-side rendering error is thrown.

What the user sees:

  • A friendly error message indicating something went wrong on the server.
  • Navigation options to return to a previous page or the portal home.

Catch-All (404 / Unknown Route)

Displayed when a user navigates to a URL that does not match any defined route in the portal.

When it appears:

  • A mistyped URL.
  • A stale or incorrect link.
  • A route that no longer exists.

What the user sees:

  • A clear "page not found" style message.
  • Links to navigate back to a known working section of the portal.

Error Boundaries

Error boundaries are placed around key sections of the portal UI. If a component fails to render due to a runtime error, the error boundary catches the failure and displays a fallback UI instead of crashing the entire portal.

This means:

  • A broken widget or section does not take down the whole page.
  • Users can continue using unaffected parts of the portal.
  • Errors are contained and surfaced in a controlled way.

Navigation from Error States

All error pages include navigation controls to help users recover without assistance:

  • Go back — Returns the user to the previous page in their browser history.
  • Go to home — Navigates to the portal's root or dashboard.
  • Contact support — Where applicable, a prompt to reach out to the agency is shown.

This ensures users are never left stranded in a dead-end state.