How long before a trace shows up in Span?​

Most sessions appear in Span within a couple of hours of finishing, and within four in the worst case. Evaluation scores and other enrichment follow a few hours after that.

The auspex agent writes each event as it happens and ships it to Span within seconds. What takes the time is the pipeline that assembles those events into a trace, which runs on a schedule rather than continuously.

What appears when

| Stage                                                              | When it appears                                                            |
| ------------------------------------------------------------------ | -------------------------------------------------------------------------- |
| The trace itself — prompts, tool calls, files edited, tokens, cost | Within 4 hours of the session, ~2 hours typically                          |
| Title and task category                                            | About 4 hours after your last message in the session, then on the next run |
| Evaluation scores                                                  | Within a few hours of the trace being classified                           |
| Environment Readiness recommendations                              | Refreshed roughly every 6 hours                                            |

A trace that shows up untitled and unscored at first is normal. Those fields fill in on later runs; nothing is lost and there is nothing to re-run.

Title and task category deliberately wait until a session has been quiet for about four hours. A session you come back to after lunch is one session, and Span would otherwise label it by what it looked like halfway through.

If it has been longer than that

- Was the machine offline? auspex holds events locally and delivers them when the machine reconnects, so a session worked on a plane appears after you are back online. Local storage holds roughly a week of activity.
- Is the feature enabled for your organization? Installing the agent is not sufficient on its own — agent traces are switched on per organization. If you have just installed auspex and nothing has ever appeared, ask your Span representative to enable it.
- Is the agent healthy? Run auspex status on the machine. It reports whether capture is wired up and whether delivery is succeeding.

If the agent is healthy, the feature is on, and a session from yesterday is still missing, contact your Span account team or support@span.app.