remotion-dev/remotion · error · Error
Expected sequence prop update result
Error message
Expected sequence prop update result
What it means
updateSequenceProps runs a codemod over a file to update Sequence element props and expects the codemod engine to return exactly one result for the single change set it passes ({nodePath, updates, schema, videoConfigValues}). If results[0] is falsy, the codemod engine produced no result despite being given a valid change set, which the library treats as an internal invariant violation rather than a user error.
Solutions
- Reload/refresh the Studio so the cached videoConfig and file contents are back in sync
- Undo external edits to the composition file so the target node matches what Studio expects
- Retry the prop update; if it persists, report the bug with the source file snippet
Defensive patterns
Strategy: try-catch
Try / catch
try {
await updateSequenceProps({...});
} catch (e) {
if (e.message === 'Expected sequence prop update result') {
// refresh Studio state and retry once, else surface as bug
}
} Prevention
- Avoid editing composition files externally while Studio visual editing is active
- Keep the source file formatted so the codemod AST matches expectations
- Retry after a Studio reload before filing a bug
When it happens
Trigger: Calling updateSequenceProps (e.g. from Studio's visual editing / update-sequence-props flow) where the underlying apply-codemod call returns an empty results array for the single change it submitted — typically because the file did not match the codemod's expected AST structure at the given nodePath.
Common situations: Editing a Sequence's props through the Studio UI when the source file has been edited externally (AST no longer matches the cached videoConfig snapshot), or when the file uses unusual formatting/constructs the codemod cannot parse into the expected node.
Understand the failure class
Background: "This is a bug, please report it": internal invariant violations, unreachable panics, and SNH errors explained — this error's family across 47 libraries.
Related errors
- Could not find as a reorder target
- Could not serialize the visual control value
- New composition ID does not match installation target
- New composition source does not match installation target
- No changes were made to the file
AI-assisted analysis of remotion-dev/remotion@46a3a6bf13 (2026-09-18).
Data as JSON: /api/errors/9123ac1b137bf7dd.
Report an issue: GitHub.
Appendix: source
Thrown at packages/studio-server/src/codemods/update-sequence-props/update-sequence-props.ts:86
schema,
prettierConfigOverride,
videoConfigValues,
}: {
input: string;
nodePath: SequenceNodePath;
updates: SequencePropUpdate[];
schema: InteractivitySchema;
prettierConfigOverride: PrettierConfigOverride;
videoConfigValues: VideoConfigValues | null;
}): Promise<UpdateSequencePropsResult> => {
const {output, results} = await updateMultipleSequenceProps({
input,
changes: [{nodePath, updates, schema, videoConfigValues}],
prettierConfigOverride,
});
const result = results[0];
if (!result) {
throw new Error('Expected sequence prop update result');
}
return {
output,
oldValueStrings: result.oldValueStrings,
formatted: true,
logLine: result.logLine,
removedProps: result.removedProps,
};
};
View on GitHub (pinned to 46a3a6bf13)