remotion-dev/remotion · error · Error
Studio sequence selection is unavailable.
Error message
Studio sequence selection is unavailable.
What it means
The provided sequenceId does not match any sequence track in the current composition's timeline. Studio flattens <Sequence> components into tracks and looks the id up; no match throws this error.
Source
Thrown at packages/studio/src/components/WebMcp.tsx:975
description: 'The sequence ID returned by get_sequences.',
},
},
required: ['sequenceId'],
additionalProperties: false,
},
annotations: {readOnlyHint: false},
execute: ({sequenceId}) => {
if (typeof sequenceId !== 'string' || sequenceId.length === 0) {
throw new Error('sequenceId must be a non-empty string.');
}
const compositionId = currentCompositionRef.current;
if (compositionId === null) {
throw new Error('No composition is currently selected.');
}
if (!canSelectRef.current) {
throw new Error('Studio sequence selection is unavailable.');
}
const timelineTrack = getCurrentTimeline().find(
(candidate) => candidate.sequence.id === sequenceId,
);
if (!timelineTrack) {
throw new Error(
`Sequence ${sequenceId} not found in the current composition.`,
);
}
const selection = getTimelineSelectionFromNodePathInfo(
timelineTrack.nodePathInfo,
);
if (selection === null) {
throw new Error(`Sequence ${sequenceId} cannot be selected.`);
}
View on GitHub (pinned to b2f4e34732)
Solutions
- Use the MCP timeline listing to get valid sequence ids for the current composition
- Add explicit id props to your <Sequence> components and use those exact strings
- Verify the id is from the currently selected composition, not another one
Defensive patterns
Strategy: try-catch
Validate before calling
const ids = getCurrentTimeline().map((t) => t.sequence.id);
if (!ids.includes(sequenceId)) { /* pick from ids */ } Try / catch
catch (e) { if (e.message.includes('not found in the current composition')) { /* re-list timeline ids and retry with a valid one */ } } Prevention
- Fetch the timeline listing before selecting by id
- Use stable explicit ids on <Sequence>
When it happens
Trigger: Calling selectSequence with a typo'd id, an id from a different composition, or an id of a sequence not currently rendered in the timeline.
Common situations: Stale ids after renaming <Sequence id>, sequences nested inside compositions that are not the selected one, or hidden/collapsed tracks that are still addressable but with different ids.
Understand the failure class
Background: 'Could not be found', 'does not exist', 'not found in database': the resource-not-found family when an ID, slug, key, or URI lookup comes back empty — this error's family across 20 libraries.
Related errors
- compositionName must be a string.
- Composition ${compositionName} not found.
- No composition is currently selected.
- Sequence ${sequenceId} not found in the current composition.
- The artifact filename ${artifact.filename} was emitted more
AI-assisted analysis of remotion-dev/remotion@b2f4e34732 (2026-08-28).
Data as JSON: /api/errors/23dbda701bc8da6f.
Report an issue: GitHub.