Skip to main content
Run SQL against your instance data lake, then save and schedule the reports you want to keep. The Queries tab holds that work: Saved, Scheduled, and History. Insights accepts one read-only DuckDB SELECT or WITH. Start from a template, or paste your own statement. That rule does not change.

​
Start a query

Click New query to open a blank editor. Set the toolbar date range for the period you care about, then paste a SELECT or WITH and click Run. Insights workbench after New query, with Untitled lake query and the Queries tab open

​
Accepted SQL queries

Insights accepts one read-only SELECT or WITH statement against the data lake. The dialect is DuckDB SQL. DuckDB functions such as TRY_CAST, DATE_TRUNC, ANY_VALUE, and BOOL_AND are available. PostgreSQL-only or MySQL-only syntax is not guaranteed to run. Any other statement is rejected. The toolbar date range chooses which days are scanned. A WHERE clause can drop rows inside those days. It cannot open days outside the range. Open Schema for tables and how they connect. Open Data Lake for how history is stored.

​
Save a query

After you run a query you want to keep, click Save. Until you save, the draft is named Untitled lake query. Saved queries live on this instance. Open one from Saved to put that SQL back in the editor. Set the date range, run a query, then save it from Actions

​
Schedule a query

Schedule query appears in Actions once the query is saved with no unsaved edits.
  1. Open Actions → Schedule query.
  2. Pick a Preset (Hourly, Daily at 09:00, Weekly on Monday, or Monthly on the 1st). The Cron expression field fills from the preset. You can leave it as is unless you need a custom schedule.
  3. Confirm Timezone, then click Save schedule.
Scheduled runs use the saved query and keep a result preview in run history. They do not send external notifications.
  • Schedules always run the last saved version. Editor changes do not run until you save again.
  • A scheduled report is the same SQL you run by hand. If a run returns empty, check the date range first.
Open Actions, choose Schedule query, pick a preset and timezone, then save the schedule

​
Reopen a past run

Use History when you want to reopen SQL you already ran on this instance, including queries you never saved. Saved is a different list: it stores the query you chose to keep, while History stores each execution. Open History on the Queries tab to reopen a past run

​
Troubleshooting

Check whether the query sums precise_amount as-is, or divides by precision first. See Precision.Also check whether it mixed currencies, or summed balances.balance across days. For live data, use the Ledger API.
Check whether balances, ledgers, or identity were collapsed to one row per ID before the join. See How they connect.
Check the toolbar date range covers both the hold and its commit or void days. You can also reference the Open inflight holds template.
Check the toolbar date range. It has to include the days you expect to see.
A column may be typed differently across days of history. Check whether dates and amounts are wrapped in TRY_CAST.
Check that the statement is one SELECT or WITH. See Accepted SQL queries.
Check the toolbar date range, how many currencies you are scanning, whether you selected *, and whether the query has a LIMIT (recommended to keep it under 5000).

​
Need help?

We are very happy to help you make the most of Blnk, regardless of whether it is your first time or you are switching from another tool. To ask questions or discuss issues, please contact us or join our Discord community.