Support Center

Monitoring Platform Errors

The Mallnline platform includes a built-in error tracking system that automatically captures crashes and unhandled errors from Visitors' browsers. As a Platform Admin, you can view, triage, and resolve these errors directly from The Tower — no external tools needed.

Where to Find Error Data

Error tracking data appears in two places within The Tower:

Overview Tab — Error Tracking Widget

The Tower Overview tab shows an Error Tracking stat card alongside your other KPIs. At a glance, you'll see:

  • Crash-Free Rate — the percentage of sessions without errors (color-coded: green â‰Ĩ95%, yellow â‰Ĩ90%, red <90%)
  • Total Issues — unique error types recorded
  • Unresolved — issues that haven't been resolved or ignored
  • Affected Users — number of unique Visitors impacted
  • Top 5 Errors — the most frequent issues with occurrence count and last seen time

Click "View All" to jump to the full Errors analytics dashboard.

Analytics → Errors Sub-Tab

Navigate to Analytics → Errors for the complete error tracking dashboard. Here you'll find:

Section What It Shows
KPI Cards Total issues, unresolved count, critical/fatal count, affected users
Issue Status Donut chart showing Unresolved vs Resolved vs Ignored
Severity Distribution Breakdown by level: Debug, Info, Warning, Error, Fatal
Issue List Sortable table of all errors with title, count, severity, last seen
Issue Detail Click any issue to expand: stack trace, tags, browser info, user context

Understanding Error Severity

Errors are classified into five severity levels:

Level Meaning Action
Debug Diagnostic information — usually harmless Review periodically
Info Informational events No action needed
Warning Potential problems that haven't caused failures yet Monitor and investigate
Error Something went wrong but the app can continue Investigate and fix
Fatal Critical failure that crashed the experience Fix immediately

Managing Issues

You can take action on any error issue directly from The Tower:

  • Resolve — Mark an issue as fixed. It won't reappear in the unresolved count unless it happens again.
  • Ignore — Dismiss a known or acceptable issue. Useful for third-party script errors you can't control.
  • Reopen — Bring a resolved or ignored issue back to the unresolved list.

TIP

Focus on errors with high occurrence counts and multiple affected users first — these have the broadest impact on Visitor experience.

What Gets Tracked

The error tracking system automatically captures:

  • JavaScript errors — runtime crashes, uncaught promises, type errors
  • Browser breadcrumbs — the trail of user actions (clicks, navigations, network requests) leading up to the error
  • Device context — browser type, OS, screen size
  • User context — the affected Visitor's handle (not personal data)

IMPORTANT

Error tracking is privacy-first. No IP addresses, cookies, or personal data are captured. User context uses handles (e.g., v|meekdenzo), not email addresses or database IDs. See Privacy, Data & Cookie Settings for our full data handling policy.

When Error Data Is Unavailable

If the Error Tracking widget shows a message instead of data:

Message Meaning
"No errors tracked yet" The error tracking system is connected but no errors have been recorded — this is a good sign!
"GlitchTip is not running" The backend error collection service needs to be started by a developer
"Authentication required" Session expired — try refreshing the page or signing in again

Frequently Asked Questions

Can I see which specific Visitor was affected by an error? Yes — click any issue to expand it, then look at the User section. You'll see the Visitor's handle and browser information. Personal details like email are never captured.

Will I be notified when new errors appear? Currently, error tracking is passive — you check The Tower for updates. Automatic alerting for new or spike errors is planned for a future release. In the meantime, check the Errors dashboard regularly during active development phases.

Can I see errors from mobile apps? The current integration tracks browser-based errors from the web frontend. Mobile app error tracking will be added when the native iOS and Android shells enter production.

Do resolved issues come back if the error happens again? Yes — if a resolved error type recurs, it will automatically reopen and appear in the unresolved count. This ensures you're always aware of regressions.

How far back does error history go? Error events are retained for 90 days by default. Older events are automatically pruned.

NOTE

For Developers: See Error Tracking (GlitchTip) for the full technical architecture, SDK integration, and Docker infrastructure. The Tower Subgraph doc covers the GraphQL API that powers this dashboard.