When to use on-demand steps
Use on-demand steps for two shapes of question:- Needle in a haystack. A lookup across a space too big to precompute — one customer’s orders among 10M rows, one ticket’s detail among thousands. The dashboard’s rollups stay precomputed; the viewer’s pick queries live.
- Fresher than the refresh. A pane whose numbers should be minutes old, not as old as the last scheduled refresh — a live status or queue depth, with or without parameters.
Adding an on-demand step
Describe the interaction to Delphina — for example, “add a dropdown of customers, and when I pick one, look up their orders live”. Delphina marks the right steps on-demand and wires the app.What viewers experience
- Selecting a value shows a Live lookup progress strip while the query runs; results typically land in a few seconds (agent steps take longer). Panes show a live · as of… badge telling viewers exactly when their numbers were produced.
- Results are cached per parameter value for a duration the app author chooses, so repeating a selection (by you or a colleague, where applicable) is instant.
- On-demand queries run under the viewer’s own data connections, not the owner’s — the opposite of refreshes. A viewer’s live lookups return exactly what their warehouse access allows, and results from credentialed lookups are private to the viewer who ran them. In workspaces where warehouse access is connected per user, a viewer who hasn’t connected theirs sees a prompt to do so instead of data.
- PDF exports capture on-demand panes as the viewer currently sees them: panes the viewer has loaded appear with their results, and panes they haven’t loaded appear empty.
Because on-demand queries use the viewer’s own access, build on-demand panes
for audiences who hold data access themselves. For dashboards aimed at viewers
without warehouse access, keep steps on the default refresh schedule — those
always run under the owner’s connections.