Back button

The ← BACK button on the left of the search toolbar is the dashboard's own history stack, independent of the browser's back button. Every search you run pushes a snapshot of the previous query, range, and saved-id onto a list. BACK pops the most recent entry and replays it.

When to use it

The most common workflow:

1. Run severity:warn and see 1,500 results.
2. Click an actor on a row to filter to severity:warn AND actor:"player:CharlesSmith". Now you see 12 results.
3. Click a sparkline bucket to filter further to a single minute. Now you see 2 results.
4. Click ← BACK to return to the 12-result actor view.
5. Click ← BACK again to return to the 1,500-result severity view.

The button stays disabled (grey) when there is nothing to go back to.

What gets saved

Each push includes:

• The full SOQL string you submitted
• The time range that was active
• The saved-query id, if you had loaded one

It does NOT save:

• The page scroll position
• Which row was expanded
• Where you were in the result pagination (cursor)

When it does NOT push history

To keep the stack clean, history pushes are skipped in three cases:

• The previous query was empty (cold start). Going BACK from your very first search would do nothing.
• The new query is identical to the previous one (re-running the same search).
• The submit was itself a BACK click (otherwise pressing BACK twice would land on the same query).

So you can mash BACK without worrying about it stalling on duplicates.

How it relates to the browser back button

The browser back button navigates between routes. From the Logs page it takes you back to wherever you came from (the projects page, the dashboard home, etc.). It does NOT undo your filters.

The Logs ← BACK button is scoped to "queries I ran on the Logs page". Use this one when you want to keep iterating on a search.

Capacity

The stack holds the last 20 queries. Older entries get dropped silently. This is enough for any single investigation session.