Query

Query keeps an editable question above its results. Select a project before building a question; no query language is required.

Choose what to find

The question starts with Find and in. Choose a node type and where to search. Leave any node and the whole project selected to search all nodes.

Choose Add a condition to extend the question:

1. Choose a field or property, a condition such as is or contains, and a value.
2. Choose And condition to require another condition in the same group.
3. Choose Or another group to add an alternative. A node must satisfy every condition in at least one group.

For example, one group can find nodes whose Name starts with North and contains harbor, while an alternative group finds nodes whose Name is Mira. Type and search area apply to both groups. A connection requirement also applies to both.

Conditions stay visible and editable above the results. Changing a type keeps existing conditions; update or remove any that are unavailable for the new type. Missing or invalid values disable the run action and show a validation message. The remove button beside a condition removes only that condition. Removing the first condition in an alternative keeps the remaining conditions in that group.

Available conditions depend on the field or property. They include is, is not, numeric comparisons, is one of, has a value, contains, and starts with. Enter comma-separated values for is one of. Date conditions use signed 64-bit timeline ticks. Selecting the current condition keeps its value; choosing a different condition clears it.

Follow connections

Choose Add a connection requirement to extend the question with and are connected to. Choose the connected node type and the connection type following through. The direction choices are relative to the nodes being found:

• are connected to accepts either direction;
• have connections to follows outgoing connections;
• have connections from follows incoming connections.

Choose Add a condition for connected nodes to limit the nodes reached by the connection. Add a condition for connections appears when the connection type has filterable properties. Use And condition and Or another group within each set. Conditions for connected nodes and connections are labeled separately.

More options contains:

• Connection distance, from direct connections to ranges of 1–5 steps;
• whether connection conditions must match Every traversed connection or Any traversed connection;
• Results per page, from 1 to 200;
• Sort matches, by name, type, created date, updated date, or unsorted.

Direct connections are the default. Longer distances can pass through intermediate nodes. Removing the connection requirement also removes its connected-node and connection conditions, while keeping the conditions on the nodes being found.

Choose search scope and time

Choose the search area after in. the whole project searches all project nodes. You can choose a focused Scope, a spatial layout, or the visible content layers sent from Atlas. History can also restore a union of several Scopes or layouts.

A focused Scope contains its selected nodes, including nodes without a Canvas placement. A spatial layout contains nodes with effective spatial manifestations. Several manifestations of the same node add it only once. Decorations and navigation links to relationships or layouts do not add nodes. An Atlas scope is the deduplicated union of the selected layouts’ memberships.

Scoped connected queries stay inside that member-node set, including starting nodes, intermediate nodes, and targets. Relationships are eligible when both endpoints are members. Overlapping content, touching layout outlines, and geometry contact do not create graph connections.

The question shows All time or the viewed project date. Queries run at the current project time. Switching project or viewed time hides the previous results and their continuation actions until you run again.

Run and continue

Choose Find nodes, or press Cmd/Ctrl+Enter within the question. Enter selects an option in a picker. Escape closes the innermost picker or options panel and returns focus to its trigger.

Changing the question does not run it automatically. The last successful results stay visible with Query changed; choose Update results to run the edited question. Loading and failures keep those previous results available. A query with no matches suggests reducing filters or widening the search scope.

After a run or More finishes, keyboard focus returns to the control you used unless you have moved elsewhere. A failed request focuses a readable, scrollable error; your question and previous results remain available to retry.

Results are grouped into:

• Matches: the starting nodes satisfying the question;
• Connected nodes: reached nodes satisfying the connected-node settings;
• Connections: relationships traversed by the matching paths.

Counts reflect the loaded results. Select a node name or connection type to open its detail. More loads another page from the last successful question. When the question has changed, More and Add to Scope still use that last successful question.

Add to Scope applies the complete query, beyond the loaded page. Add once pins every matched and connected node at the query’s scope and viewed time. Keep updated saves a dynamic rule; it is available for whole-project queries and follows the all-time graph. Connections remain query results rather than Scope members. See Scopes for removal and update behavior.

While adding a query, the Scope choice, mode and closing controls wait for the request to finish. A failure keeps your choices and focuses the error inside the dialog. Correct the choices or try the same action again.

Revisit a previous question

Open History in the page header and select a previous query to load its question and settings. It runs only when you choose the run action, using the current viewed time. History has no rename, manual-save, or delete action.

Saved conditions that cannot be represented by the sentence builder keep their original grouping and values and appear as a readable summary. Choose Remove saved conditions before replacing that set of conditions; other conditions and settings remain. Unavailable saved types and search scopes stay visible and must be replaced with available choices before running.