Platform capability

Return to prior questions and run history

Save SQL queries by connection, re-run them with one action, review past results, and share specific runs with teammates.

Scope: Per connection
History: Run logs + results
Sharing: Shareable run links

Saved queries are scoped to team connections. Sharing exposes the specific run result, not live query access.

Illustrative interface

Platform capability

Saved Queries

Northstar Postgres / saved query

Monthly revenue by region

RUNS: 14
LAST RUN: 2 hours ago

Query

SELECT
  region,
  SUM(amount) AS revenue,
  COUNT(*) AS orders
FROM public.orders
WHERE created_at >= date_trunc('month', now())
GROUP BY region
ORDER BY revenue DESC;

Most recent run result

Illustrative values

Illustrative most recent run result
Region	Revenue	Orders
North America	Illustrative $1,248,320	8,412
Europe	Illustrative $843,100	5,891
Asia Pacific	Illustrative $612,750	4,203

North America
REVENUE
Illustrative $1,248,320
ORDERS
8,412
Europe
REVENUE
Illustrative $843,100
ORDERS
5,891
Asia Pacific
REVENUE
Illustrative $612,750
ORDERS
4,203

Illustrative result -- data controls disabled

Saved queries collect the SQL you return to. Each query belongs to a connection, keeps a log of every execution, and lets you share a specific run result without giving the recipient live access to the database.

Save a query, find it later

When a query is worth keeping, save it from the console. It appears in the sidebar under its connection, named and ready to open. The list stays short because it is scoped per connection -- you see only the queries that belong to the database you are working in. Open a saved query to load its SQL into the console, adjust parameters if needed, and run it again.

Review run history

Every execution of a saved query is logged with its timestamp, duration, row count, and completion status. Use the run history to compare results across time, spot a query that started failing, or confirm what a previous run actually returned. Failed runs are recorded with the same detail so you can see when something broke without re-running it to find out.

Share a specific run result

Select a completed run and generate a share link. The link gives the recipient access to that run's result -- the rows, the timing, and the query text at the time of execution. It does not grant console access or the ability to re-run the query against the live connection. Use it to hand off evidence, not access.

Saved queries / run history

Every execution logged. Any run shareable.

Illustrative run history

Each run records the timestamp, duration, row count, and status. Select a completed run to generate a share link that exposes the result, not the live connection.

Sample data -- no live execution

Query: Monthly revenue by region

5 runs shown

Illustrative run history for a saved query
Run	Timestamp	Duration	Rows	Status	Share
run_0047	2026-09-02 14:32 UTC	1.8s	3	completed
run_0046	2026-09-01 09:15 UTC	2.1s	3	completed
Shareable link (illustrative) https://data.synehq.com/share/run_0046 Access View this run's result only. No live query access.
run_0045	2026-08-29 16:48 UTC	0.4s	0	failed	--
run_0044	2026-08-28 11:02 UTC	1.6s	3	completed
run_0043	2026-08-25 08:30 UTC	1.9s	4	completed