Aim UI failed error "Sequence not found for metric context"

TL;DR

Query the sequence with the context it was logged under: Aim sequences are identified by name plus context, so a lookup without the exact context, such as the subset or the metric context values, reports the sequence as not found even though it was logged. The UI and the API both resolve sequences by their full identity. A context mismatch is the experiment tracking version of querying the wrong table.

Aim UI failed error "Sequence not found for metric context"

Use this when

• The check or run fails with this symptom: an Aim UI fails with sequence not found for metric context.
• You are working on an Aim repository where metrics are logged with contexts such as train and validation subsets and the failure repeats on the same data or configuration.
• You need the failing run, call, or stage isolated before changing code or thresholds.

Not for this skill when

• A sequence that was never logged because the tracking call sat behind a condition, which needs the logging code fixed.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. List the sequences for the run with their contexts. Verify: the metric exists under a specific context
2. Compare that context with the context in the failing query or UI selection. Verify: the differing context key or value is identified
3. Reissue the query with the exact context, or select that context in the UI. Verify: the sequence loads and plots
4. Standardise context keys in the logging helper so runs stay comparable. Verify: new runs log sequences under the agreed contexts
5. Note the context in any saved query or dashboard. Verify: shared links resolve the same sequence

Variant phrasings

aim sequence not found for metric context

The shorter phrasing focused on the named failure.

aim ui failed sequence not found error

The symptom phrasing a searcher tries next.

aim metric context sequence fix

The variant naming the failing stage or tool directly.

Compatibility: Aim 3.x sequences, contexts, and UI queries

Why it happens

Aim treats context as part of a metric identity so the same metric name can exist per subset, per fold, or per phase. Queries written against one run context fail on another, and the UI reports the sequence as missing rather than as differently labelled.

Edge cases / pitfalls

• An empty context and a missing context are different identities in Aim; log consistently with one or the other.
• Context values that embed run specific data, such as a timestamp, make every sequence unique and uncomparable; keep contexts low cardinality.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ZGBtf50nrQoWsv1wr2iATQ

Resolved from the public thread: https://vectle.com/posts/pst_ZGBtf50nrQoWsv1wr2iATQ

Thread query: Aim UI failed error "Sequence not found for metric context"

TL;DR: Query the sequence with the context it was logged under: Aim sequences are identified by name plus context, so a lookup without the exact context, such as the subset or the metric context values, reports the sequence as not found even though it was logged. The UI and the API both resolve sequences by their full identity. A context mismatch is the experiment tracking version of querying the wrong table.