ServerOps.ggbeta
GuidesLogsDashboard

Saved queries

Pin queries you run often so they are one click away from the left rail.

Saved queries

The left rail of the Logs page holds your saved queries: queries you have explicitly chosen to keep. They are stored on the server and shared with anyone who has access to the project, so a moderator who saves a useful query exposes it to the rest of the staff team.

Saving a query

  1. Write or refine a query in the search bar.
  2. Click the ↗ SAVE button in the toolbar.
  3. A small inline form appears below the toolbar. Type a short name (e.g., "Errors today" or "Charles RDM check").
  4. Press the SAVE button on the form, or hit Enter.

The new entry appears at the top of the SAVED QUERIES list. The breadcrumb gains a small orange suffix showing the saved name, and the URL gets a ?saved=q_... parameter so refreshing the page keeps you on the same view.

Loading a saved query

Click any row in the SAVED QUERIES list. The search bar fills with that query's SOQL, the URL updates, and the search runs immediately.

If you arrive on the Logs page via a URL containing ?saved=q_... (for example, a permalink a teammate sent), the page resolves the saved query server-side and runs it for you on load.

Editing a saved query

There is no in-place edit. To change a saved query:

  1. Load it (click it in the rail).
  2. Edit the SOQL in the search bar.
  3. Save again with the SAME name (this creates a fresh entry; the old one stays).
  4. Delete the old one from the rail when you are happy.

This avoids the "saved query silently changes underneath everyone else who relied on it" failure mode.

Deleting a saved query

Hover over any saved-query row. A small button appears on the right side of the row. Click it.

A confirmation modal opens (the same style used for deleting an org or media file). The button is intentionally destructive-styled because deletion is server-wide: anyone who had bookmarked the URL with ?saved=q_... will lose the deep link.

Limits

  • Maximum 100 saved queries per project.
  • Maximum name length 100 characters.
  • Maximum SOQL length 4096 characters (same as the search bar itself).

If you hit the cap, the save form surfaces an error: "Each project may hold at most 100 saved queries." Delete some old ones to make room.

What is NOT saved with the query

The saved entry stores only the SOQL string. It does NOT save:

  • Your time-range selection (the picker)
  • The currently expanded row
  • Your scroll position
  • Multi-line editor toggle

The time range is part of the URL though, so a permalink (?saved=...&range=7d) does carry the range. See Permalinks and Discord copy.

On this page