Active Chains — live orchestration view
When Nexus orchestrates multiple lims on one request, you see a live pipeline on the Dashboard showing exactly what's happening, step by step.
What a chain looks like
At the top of your Dashboard, the Active Chains section shows every multi-lim task currently running. Each chain has:
- Title — short summary of the user request
- Status — running / completed / failed
- Progress — "2/3 steps done"
- Steps — ordered boxes with arrows between them, each showing the lim responsible, their current status, and their brief output
Example:
Aria finished research, Marcus is drafting the post, a third step is queued.
[✓ Aria] → [⏳ Marcus] → [○ pending]Aria finished research, Marcus is drafting the post, a third step is queued.
Status icons
- ○ pending — waiting on a prior step's output
- ⏳ running — lim is actively working (pulsing)
- ✓ completed — step finished successfully
- ✗ failed — step errored; overall chain status may still complete if other steps succeeded
Why chains matter
- Observability: you see what's happening across 3+ lims at once without context-switching
- Accountability: each step has a lim's name on it — you know who did what
- Debugging: when a chain fails, you see which step broke and why
Under the hood
Every task in an orchestration shares a correlationId that groups them into a chain. Each step has a parentTaskId pointing at the root request. This structure lets the Dashboard reconstruct the chain in real time and lets Nexus audit the history of any multi-lim run.
Chains are retained briefly
Completed chains stay visible for ~10 minutes so you can see the outcome. Then they drop off the Dashboard (but stay in Analytics history).