fundamentals retail

Status, delays, and "is it broken?"

How to tell a busy system from a broken one—using IRIS Status, timestamps, and FAQs without becoming a network engineer.

First checks (under two minutes)

  1. Open Status in IRIS (/status in your deployment) and see whether dependent services report healthy for your org’s layout.
  2. Find the analysis timestamp on the symbol—old timestamps mean stale, not necessarily down.
  3. Retry once after a few minutes; burst traffic and batch queues routinely add latency.

When to use FAQ vs Help

  • FAQ & troubleshooting (guide) covers recurring product behaviors: missing symbols, odd error strings, delay expectations.
  • Help in IRIS (your support property when configured) is for account issues, billing, or incidents that need a human.

Mindset

Most “it must be broken” reports are freshness or universe issues—fixable by rerunning analysis or widening the symbol set—not mysterious outages.

Educational disclaimer

TRINITY provides tools and education, not personalized investment advice. Consult a qualified professional before making financial decisions. See Disclosures.

Progress is saved in this browser. Cloud sync requires PUBLIC_IRIS_API_BASE, IRIS CORS allowlist, and window.__trinityIdToken.