remotion-dev/remotion · error · Error

The function name ${input.functionName} does not adhere to t

Error message

The function name ${input.functionName} does not adhere to the function name convention (https://www.remotion.dev/docs/lambda/naming-convention).
Cannot determine memory and disk size from the function name.
You must call getRenderProgress with `skipLambdaInvocation` set to false.

What it means

When getRenderProgress is called with skipLambdaInvocation:true, it avoids invoking the Lambda to read memory/disk config and instead parses those values out of the function name via parseFunctionName. If the function name does not follow Remotion's naming convention, parseFunctionName returns null and this error is thrown because memory/disk cannot be determined without invoking.

Source

Thrown at packages/lambda-client/src/get-render-progress.ts:32

	region: AwsRegion;
	logLevel?: LogLevel;
	s3OutputProvider?: CustomCredentials<AwsProvider>;
	forcePathStyle?: boolean;
	skipLambdaInvocation?: boolean;
	requestHandler?: RequestHandler;
};

/*
 * @description Gets the current status of a render originally triggered via renderMediaOnLambda().
 * @see [Documentation](https://remotion.dev/docs/lambda/getrenderprogress)
 */
export const getRenderProgress = async (
	input: GetRenderProgressInput,
): Promise<RenderProgress> => {
	if (input.skipLambdaInvocation) {
		const parsed = parseFunctionName(input.functionName);
		if (!parsed) {
			throw new Error(
				[
					`The function name ${input.functionName} does not adhere to the function name convention (https://www.remotion.dev/docs/lambda/naming-convention).`,
					'Cannot determine memory and disk size from the function name.',
					'You must call getRenderProgress with `skipLambdaInvocation` set to false.',
				].join('\n'),
			);
		}

		return getProgress<AwsProvider>({
			bucketName: input.bucketName,
			renderId: input.renderId,
			region: input.region,
			forcePathStyle: input.forcePathStyle ?? false,
			customCredentials: input.s3OutputProvider ?? null,
			expectedBucketOwner: null,
			providerSpecifics: awsImplementation,
			memorySizeInMb: parsed.memorySizeInMb,
			timeoutInMilliseconds: parsed.timeoutInSeconds * 1000,

View on GitHub (pinned to 78fe4bb3fd)

Solutions

1. Omit skipLambdaInvocation (or set it to false, the default) so getRenderProgress queries the function directly for memory/disk
2. Use a function name produced by deployFunction that follows the documented naming convention

Example fix

// before
await getRenderProgress({ functionName: 'my-custom-name', skipLambdaInvocation: true, ... });

// after
await getRenderProgress({ functionName: 'remotion-render-...-2048mb-2048mb', skipLambdaInvocation: false, ... });

import {parseFunctionName} from '@remotion/lambda-client';
// before calling with skipLambdaInvocation
if (skipLambdaInvocation && !parseFunctionName(functionName)) {
  throw new Error('function name does not follow Remotion convention; set skipLambdaInvocation=false');
}

const isConventionName = (name: string): boolean => Boolean(parseFunctionName(name));

When it happens

Trigger: Calling getRenderProgress({skipLambdaInvocation:true}) with a functionName that was not produced by deployFunction (custom name or older naming scheme).

Common situations: Custom/renamed function, pointing at a function deployed by an older Remotion version with a different naming format, hand-written function name.

Related errors

• 'function_name' parameter is required and cannot be empty or
• Image format mismatch: ${outName} was given as the ${outName
• Image format mismatch: ${outName} was given as the ${outName
• Pass --s3-output-provider-endpoint when using S3 output prov
• Pass --force-bucket-name when using S3 output provider flags

AI-assisted analysis of remotion-dev/remotion@78fe4bb3fd (2026-08-12). Data as JSON: /api/errors/5fa37015e74f2b2a. Report an issue: GitHub.