Skip to main content

​
Summary

The Logs page can appear slow or unresponsive even when the status page is OK. Use the checks below to troubleshoot the problem.

​
What is happening

Saved log views retain filters and column display settings. Custom column expressions are stored separately. An invalid custom column expression can cause the Logs rows query to fail. Broad filters such as input IS NOT NULL can cause slow scans. The platform status page reports overall system health. It can be OK while a project’s Logs page is slow or unresponsive.

​
Fix or suggestion

​
Option 1: Reset the current All logs view settings

  1. Go to Logs.
  2. Select All logs view from the view selector to reset its settings. This does not edit or delete custom column expressions.
  3. Retry loading the Logs table.

​
Option 2: Remove or simplify custom columns and filters

  1. Open the view that was slow.
  2. If a custom column has an invalid expression, edit or delete it in Display. Editing or deleting a custom column also affects other Logs views that use that column.
  3. Remove or simplify broad filters such as input IS NOT NULL.
  4. If you have project Update permission, use Save view as to save the changed filters and display settings under a new name.
If the table is still slow, select Past 15 minutes and retry loading it. If the issue persists after these steps, contact support and include the affected view name, a screenshot of the slow state, and the approximate time range you used.

​
How to confirm it worked

  • Return to All logs view with Logs and Past 1 hour selected, and check that the Logs table loads normally.
  • If custom columns remain, check that they display expected values.

​
Notes

  • Personal default views are stored in your browser. Clear personal default view removes your personal default selection without editing or deleting custom column expressions.
  • Avoid using untested custom column expressions in your default view.