remotion-dev/remotion · error · Error

Sequence ${sequenceId} not found in the current composition.

Error message

Sequence ${sequenceId} not found in the current composition.

What it means

Even when the sequence track exists, Studio must be able to derive a valid timeline selection from the track's nodePathInfo. If that mapping returns null (the track cannot be selected as an item), this error is thrown.

Source

Thrown at packages/studio/src/components/WebMcp.tsx:982

					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.`);
						}

						selectItems([selection], {reveal: true});
						return Promise.resolve({
							currentContent: currentContentRef.current,
							selectedSequence: serializeSequence(timelineTrack),
						});
					},
				},

View on GitHub (pinned to b2f4e34732)

Solutions

1. Target a concrete <Sequence> element's id instead of the composition root track
2. Pick a different sequence that corresponds to an actual JSX node
3. Update Remotion — selection derivation for some tracks may be supported in newer versions

const track = getCurrentTimeline().find((t) => t.sequence.id === sequenceId);
if (getTimelineSelectionFromNodePathInfo(track.nodePathInfo) === null) { /* choose a selectable sequence instead */ }

catch (e) { if (e.message.includes('cannot be selected')) { /* fall back to selecting a nested child sequence */ } }

When it happens

Trigger: Calling selectSequence on a track whose nodePathInfo cannot produce a selection — e.g. a root-level or synthetic track that is not individually selectable in the timeline UI.

Common situations: Selecting a top-level composition wrapper track or a track created by Studio internals rather than a user <Sequence>.

Related errors

• No composition is currently selected.
• Composition ${compositionName} not found.
• Studio sequence selection is unavailable.
• The artifact filename ${artifact.filename} was emitted more
• compositionName must be a string.

AI-assisted analysis of remotion-dev/remotion@b2f4e34732 (2026-08-28). Data as JSON: /api/errors/f77503068c32eef6. Report an issue: GitHub.