Nightly insights

Nightly insights controls the work Querri does on a workspace’s Library overnight. As the page puts it: “What your assistant looks at overnight, how much thinking it may do, and what it found last time.”

Who can see this: admins only. Open it from Settings › Workspaces, pick a workspace, then its Nightly insights tab. An old link to the settings page still works; it takes you to your company workspace’s tab.

Every setting here belongs to one workspace. Each one has its own schedule, budget, history and queue, and a run only ever reads that workspace’s data and questions. Your organization’s credit limits still apply across all of them.

Which workspaces run it:

Your company workspace carries on with whatever your organization was already set to.
Workspaces you’ve made start with scheduled runs off. Turn one on here when you want it.
Private workspaces never run it, on a schedule or by hand.

Nightly credit budget: how many credits the pass may spend in a night.
What it looks at: the parts of the pass, each with its own switch.
How often: Automatic, Daily, Weekly or Off.
Run tonight’s pass now: run the pass once, straight away.

The nightly pass only recommends. “Results always land in your Inbox for approval.” Nothing it finds joins your Library until someone accepts the card.

There’s no Save button. Each budget button, switch and frequency button saves the moment you click it. If your provider has locked a setting, its buttons are turned off and the page says “This setting is managed by your Querri operator.”

Nightly credit budget

“One credit is one analysis.” Choose 0, 1, 2, 3, 5, 8 or 10. The default is 3, about three analyses a night. At 0 the pass is still scheduled, but it does no thinking.

After a pass has run, this section tells you how many credits last night used out of your budget and how many your organization has left this period. It also shows how many questions are queued for tonight, highest value first, and which one is next.

The pass never spends more than your organization has left. If there were no credits left, the page says last night’s pass ran no analyses. Questions it doesn’t get to wait for another night, and they’re dropped after seven.

Credits the pass spends are reported as system usage, and See usage opens Monitor Usage. A person’s monthly credit limit never stops the pass.

What a credit buys.
Last night’s spend, and the credits your organization has left.
What’s queued for tonight, when anything is.
See usage: where the spending shows up.

Keep credit use predictable covers sizing the budget.

What it looks at

“Each part runs in order and shares the budget above. Turn one off and its credits go to the rest.” (default) next to a part means nobody has changed its switch.

Part	What it does	Default
Review existing answers	Group what your team asked this week and decide, per theme, whether an answer already exists or one should be built.	On
Find missing questions and views	Look for questions nobody has asked yet that your data can answer, from coverage gaps, demand and feedback.	On
Profile data and joins	Measure column health, find joins between sources, and spot the same business entity living in two systems.	On
Watch metrics	Read each metric’s own history and raise a card when it moves in a way that history says is unusual.	On
Curate new data	Take another pass over recently added data and propose what is now answerable but still unanswered.	Off

Curate new data starts off because the same review already runs when new data arrives.

Watch metrics looks at your KPIs. When one moves in a way its own history says is unusual, it files a Worth watching card in the Inbox, and accepting that card sets up a monitor on the KPI.

Review existing answers, tagged (default) because nobody has changed its switch.
A part’s switch, here the one for Find missing questions and views.

How often

Automatic, the default: “Every night for the first week, then weekly while someone opens the Inbox. Pauses after two weeks unread.”
Daily: “The assistant reviews every night.”
Weekly: “One pass a week.”
Off: no scheduled passes, and manual runs only.

Scheduled passes run overnight. Automatic is the one to leave alone if you’re unsure: it works hard while the Inbox is being read and stops spending when nobody is reading, rather than running every night regardless.

Run tonight’s pass now

“Runs exactly what is set above, once. It can take several minutes.” The pass starts as soon as you click, with no confirmation, and it spends credits up to your budget. A notice sends you to the Inbox to watch its progress, with an Open Inbox link.

Last run counts Analyses, Credits used, Cards written and Held back. A line under it says how many analyses were done, how many questions are queued for tomorrow and how many were dropped after seven nights. Before any pass has run, it reads “No pass has run yet.”

Run tonight’s pass now: runs once, right away.
The last run’s Analyses, Credits used, Cards written and Held back.
The line under them: how many analyses were done and how many questions are queued for tomorrow, plus any that were dropped.

Build and clean up

This section has two runs you start by hand, plus a choice about whether they act on their own. The choice doesn’t touch the nightly pass: “The nightly pass above always recommends, whichever is selected.”

Require confirmation: “The agent will recommend; you create each view.”
Auto-build: “The agent will build the views it judges worth creating, and retire the duplicates it finds.”

Which one is on right now? Check before you start a run. The choice is saved in this browser only, so another admin, or you in a different browser, might be on the other setting. Clearing your browser data puts it back to Require confirmation.

The two runs:

Run discovery reviews up to 4 clusters of questions your team has asked, and works out whether the Library needs new views.
Clean up duplicates finds groups of near-duplicate views, and the Librarian reviews each group. It runs only when someone clicks it, never as part of the nightly pass.

Both start the moment you click, and you follow them in the Inbox. With Require confirmation, the verdicts wait there: build recommended comes with Create this view, and retire recommended comes with Retire these. With Auto-build, the Librarian builds the views and retires the duplicates itself. Either way, a view that other views or projects use isn’t retired.

The Inbox shows verdicts from the newest run only, so review what Clean up duplicates recommends before the next nightly pass replaces it.

Duplicate collections, and views that answer no question, are a separate matter. The nightly pass files those as Cleanup cards in the Inbox.

Require confirmation or Auto-build: whether the runs below act on their own.
Run discovery and Clean up duplicates: the two runs you start by hand.