Skip to main content

Performance Troubleshooting

This guide covers common performance issues across The One Stack, including slow page loads, timeouts, and search problems.

Slow Page Loads​

Symptom: Pages take more than a few seconds to load, or the loading spinner persists for a long time.

Debugging Steps​

  1. Check your internet connection — Run a speed test at fast.com. The One Stack requires a stable connection with at least 5 Mbps download speed.
  2. Try a different browser — If the issue is isolated to one browser, it may be caused by extensions or browser-specific rendering issues.
  3. Clear browser cache — Cached stale assets can cause rendering problems. Clear your cache and reload.
  4. Check the Status Page — Visit status.theonestack.com to see if there is degraded performance on any service.
  5. Reduce open tabs — If you have many The One Stack product tabs open simultaneously, your browser may be running low on memory.

Browser Requirements​

For the best experience, use a modern Chromium-based browser (Chrome, Edge, Brave) or Firefox. Safari is supported but may have slower performance with complex dashboards.

Minimum recommended specs:

  • 4 GB RAM available for the browser
  • Hardware acceleration enabled
  • JavaScript enabled (required)

Dashboard Widget Timeouts​

Symptom: One or more dashboard widgets show "Failed to load" or a timeout error.

Debugging Steps​

  1. Refresh the dashboard — Individual widget failures are often transient.
  2. Check the specific product — Navigate directly to the product whose widget is failing. If the product itself is slow or down, the widget will also fail.
  3. Reduce widget count — If you have many widgets on your dashboard, try removing some to see if the issue is caused by too many concurrent data requests.
  4. Check your subscription — Widgets for products you are not subscribed to will fail to load.

Widget Timeout Thresholds​

Each dashboard widget has a 10-second timeout. If the underlying product API does not respond within 10 seconds, the widget shows an error. This is typically caused by:

  • Temporary API latency
  • Large datasets being aggregated (e.g., a ticket count widget across thousands of tickets)
  • Network issues between your browser and the product API

Search Not Returning Results​

Symptom: The search bar returns no results or incomplete results.

Debugging Steps​

  1. Wait for indexing — After creating or updating records, the search index updates within 30 seconds. If you just created the item, wait and try again.
  2. Check your search scope — Some search bars are scoped to the current product. Use the global search (Hub search bar) to search across all products.
  3. Try different search terms — Search supports partial matches on names, emails, and key fields. Try a shorter or different portion of the term.
  4. Check filters — If you have active filters or are viewing a filtered list, search results are limited to items matching those filters.
  5. Check permissions — You can only search for items your role has permission to view.

Large Dataset Handling​

Symptom: Lists, reports, or exports are slow or timing out when you have a large number of records.

Best Practices​

  1. Use filters — Always apply filters before loading large lists. Filtering happens server-side and significantly reduces the data transferred.
  2. Use pagination — Avoid loading "All" records at once. The default page size is optimized for performance.
  3. Export in background — For large exports (10,000+ records), use the "Export" button which processes in the background and emails you a download link when ready.
  4. Schedule reports — Instead of running ad-hoc reports on large datasets, schedule them to run during off-peak hours.

Known Limits​

OperationRecommended MaxHard Limit
List view page size100 records500 records
Search results50 results200 results
CSV export50,000 records100,000 records
Report date range90 days365 days
Dashboard widgets12 widgets20 widgets

Network and Connectivity​

If you are consistently experiencing performance issues, check the following:

  1. Firewall rules — Ensure your firewall allows traffic to *.theonestack.com and product-specific domains.
  2. Proxy settings — If you use a web proxy, ensure it is not adding latency or blocking WebSocket connections (required for real-time updates).
  3. DNS resolution — Try using a public DNS resolver like 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) to rule out DNS issues.
  4. VPN — If you are on a VPN, try disconnecting to see if performance improves. Some VPNs add significant latency.