Query history
Every query that runs is kept with what it returned and what it cost. Save a query by title to find it again, and run the same query again whenever you want.
What is saved
A query is what to calculate. A query result is the data that came back. Every query of the workspace is kept in its history, whether an AI tool, an API key or the app ran it. A query becomes a saved query when you give it a title, in the app or by asking your AI tool.
| Field | What it holds |
|---|---|
| Statement | The exact query that ran, with the values of its parameters |
| Who | The member it ran for, and the AI tool or the API key that submitted it |
| When | When it was submitted, when it started and finished, and how long it ran |
| Cost | The query credits it used, the peak memory it needed and the memory limit of the plan |
| Outcome | Finished, stopped (it needed more memory or time than the plan allows, or it was cancelled) or failed |
| Result | The first rows of the result, the number of rows, and the full result as a Parquet file while it is kept |
A query that was refused before it started, for example because the member's query credits were used, leaves no record.
Saved queries
A saved query is a read-only query with a title, an optional description and optional parameters, stored for the whole workspace. A parameter is a named, typed value in the query, written $name, so the same query can run for another week or another product without editing its text. Any member can save, rename and run a saved query, and archive it; archiving is final.
A member can save a query while the workspace has fewer unarchived saved queries than the member's plan allows: 20 on Free, 200 on Pro, 2,000 on Max. Archived queries do not count.
Run a query again
Each query has an id. Choose Run again on it in the app, or give the id to your AI tool, to run exactly the same statement. A saved query runs with its parameter values, or with the defaults.
- Running again uses query credits like any other query, and the same memory limit applies.
- Looking at a stored result is free: nothing is recalculated.
- A run is a new query of its own, with its own result. The earlier result stays as it was.
- Late-arriving events can change an old period, so a stored result shows what was known when the query ran.
Show my queries from last week.
Run the saved query "signup funnel" again for this week.
Who sees the history
- Every member sees every query of the workspace, including the ones run with an API key.
- A member's name stays on the queries they ran for 90 days after they leave the workspace, then the history shows "former member".
- Any member can delete a query: its result file is removed within about a minute, and the record stays in the history marked as deleted. Nobody can edit a query.
Exports
An export writes a whole result to a file, as Parquet, CSV or JSON lines, for use outside Tuumo. It is a query like the others, and it is kept in the history in the same way. A plan limits the rows of an export: 1,000,000 on Free, 50,000,000 on Pro and none on Max. When the limit cuts an export, the answer says so.
CSV cells are written as stored, so a spreadsheet may read a cell that starts with =, +, - or @ as a formula. Use Parquet or JSON lines for a file a spreadsheet opens.
Retention
- A result file is kept for the plan of the member who ran the query: 7 days on Free, 30 days on Pro and 90 days on Max. After that the query reads as expired, and running it again gives a fresh result.
- A link to download a result works for 15 minutes; ask for a new one when it has expired. The link is a secret: anyone who has it can download the file, so do not share it; hand on the file instead.
- The record of the query, with its statement, cost and outcome, stays in the history, also after the query is deleted, until the workspace is destroyed, 30 days after the workspace is deleted.