App catalog

Open Apps in Horizon's sidebar to browse published notebook apps. Home also shows a short Your apps list. Browsing reads app metadata and does not start notebook compute or load the publisher's live data.

The catalog uses your active organization, workspace, and environment. Search matches the app's title, name, and description. Use Show more to continue a long result list.

Every filter also applies your current platform permissions and clearance. Changing filters never reveals a hidden app. An empty list can mean that no published app matches your scope, audience, search, or filter.

Cards show the current release and publisher or extension provenance. The illustration is a neutral layout icon, not a screenshot of someone else's data. Run access restricted describes the app's audience. Absence of that label does not grant access to its underlying objects or actions: runtime admission must check your permissions and the release's declared resources separately.

Withdrawal removes an app from discovery and revokes its open sessions. Authors withdraw an app from Publish as app in the notebook that published its current release. Unpublished notebook edits do not change a card's current release. Refreshing the catalog rechecks your session and permissions; an unavailable state is distinct from an empty result.

Choose New app to open the ontology and starter selection in Analytics. Authors manage validation and publication from Analytics notebooks.

Open an app to start its published notebook. The viewer keeps that release until you choose Open available update. Share copies an authenticated link and grants no additional access. Open in notebook appears only with source editing permission. Session expiry, denied renewal, workspace changes, and departure remove the app frame; retry creates a fresh session.

Reloading the page resumes the app in the same tab instead of starting it again, as long as its session has not expired; your permissions are checked again when it resumes. A new tab always starts its own session. A tab you close keeps its session for up to a minute before it ends.

An app uses the Scrydon colors and follows your light or dark theme as it was when the app opened. If you switch themes while an app is open, the change applies the next time you open it.

Declared SDK tables read ontology data under your permissions and periodically reconcile it. Failed reads clear their rows and selection and retry while the session remains authorized. Source health is qualified separately: supported polling sources need recent, complete ingestion evidence for their current configuration. Missing evidence stays unknown and expired or failed evidence is degraded. Creating an app never establishes source health.

The app bar shows the source freshness of everything the app has read. Sources live appears only when every query the app is currently reading reported healthy sources. A widget the app has stopped reading holds the bar at unknown for 15 seconds, which covers a read that is retrying, and is then ignored. Sources stale appears when any source's evidence has expired or failed. Source health unknown covers everything else: before the first read, after a failed read, and for data with no ingestion evidence, such as objects stored directly in the ontology. Only a complete poll counts as evidence. A poll that succeeds but rejects or does not deliver some rows leaves health unknown. A failed poll, including one whose track positions could not be published, shows the source as stale. Evidence expires two poll periods after the source's last complete poll started. The period is the interval set on the installed source, or the definition's interval when none is set. Changing a source's configuration, including its interval, returns it to unknown until its next complete poll. Horizon rechecks it about every five seconds while the app is open, so a stopped feed turns stale shortly after that window. Freshness is separate from the runtime state beside it: a running app can show stale sources. The complete multi-source COP remains in development.

When an authored alert list offers View response in Horizon, select an alert and use that control to check its response. Horizon displays Open response above the notebook only if you can access both the detection and its recorded flow. Click the link to open it. The lookup does not create or advance a flow. An unavailable message does not distinguish missing responses from restricted ones. Changing selection, losing data or ending the session clears the result; it also expires after 30 seconds. Request a fresh lookup to try again.