Skip to main content

App too slow due to computation

This article explains how to temporarily disable computed columns so you can regain access to your data and fix an issue.

Updated yesterday

If your app is running very slowly in the Glide Builder, the issue is often caused by a computed column that takes too long to calculate. When this happens, it can be difficult to load the Data Editor, making it hard to find, edit, or delete the column responsible for the slowdown.


Why computed columns can slow down your app

Computed columns (such as Lookups, Relations, Rollups, Math, Query, or JavaScript columns) recalculate whenever data changes. If a computation is complex or depends on large datasets, it can significantly slow down the Builder and, in some cases, prevent it from loading properly.


Temporarily disable computed columns

You can load your app’s Data Editor without running computed columns by adding a URL parameter.

Use the following URL format:

https://go.glideapps.com/app/appid/data?computedColumns=false

Replace appid with your actual App ID.

Steps

  1. Open your browser and paste the URL above, making sure to use your app’s App ID.

  2. Press Enter to load the page.


What happens when computed columns are disabled

When computedColumns=false is applied:

  • All computed columns will appear empty because calculations are not running.

  • All basic columns (stored values from your source tables) will still display normally.

  • The app structure and tables will continue to load, allowing you to navigate the Data Editor.

This makes it possible to safely access your data even if a computation was previously blocking the Builder.


Edit or delete the slow column

With computed columns disabled:

  1. Locate the computed column that is causing the slowdown.

  2. Edit the column to simplify its logic, or delete it entirely.

  3. Remove ?computedColumns=false from the URL.

  4. Reload the Builder to restore normal computation behavior.


Troubleshooting tips

  • Make sure computedColumns=false is spelled exactly as shown.

  • Verify that you are using the correct App ID.

  • If the Builder still struggles to load, try refreshing the page or opening the link in a private/incognito window.

This approach allows you to recover access to your app’s data and resolve performance issues caused by expensive computations in Glide.

Did this answer your question?