Skip to content

@remotion/lambda-client: Handle empty Lambda response payload#6509

Merged
JonnyBurger merged 2 commits intoremotion-dev:mainfrom
wistia:handle-empty-lambda-payload
Feb 13, 2026
Merged

@remotion/lambda-client: Handle empty Lambda response payload#6509
JonnyBurger merged 2 commits intoremotion-dev:mainfrom
wistia:handle-empty-lambda-payload

Conversation

@acj
Copy link
Contributor

@acj acj commented Feb 11, 2026

We've seen this error occasionally when we've hit our account-level Lambda concurrency limit:

TypeError: The \"list\" argument must be an instance of SharedArrayBuffer, ArrayBuffer or ArrayBufferView.
    at TextDecoder.decode (node:internal/encoding:471:16)
    at callLambdaSyncWithoutRetry ([...]/node_modules/@remotion/lambda-client/dist/cjs/index.js:68876:44)

The payload is passed straight to decode without being checked, which seems to be the source of the type error.

My hunch is that the status code is 429 and that FunctionError is empty (skipping the existing guard) because it's an error from the Lambda service rather than from the Remotion function. I'm still trying to get a clean repro, though. If that hunch is correct, do you want me to use TooManyRequestsException in the error string so that the friendly error message handling sees it?

Thanks!

@vercel
Copy link
Contributor

vercel bot commented Feb 11, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
bugs Ready Ready Preview, Comment Feb 11, 2026 9:25pm
remotion Ready Ready Preview, Comment Feb 11, 2026 9:25pm

Request Review

@acj acj force-pushed the handle-empty-lambda-payload branch from 9d6097b to c14dc5e Compare February 11, 2026 21:22
@JonnyBurger JonnyBurger changed the title Handle empty Lambda response payload @remotion/lambda-client: Handle empty Lambda response payload Feb 13, 2026
@JonnyBurger JonnyBurger merged commit 80228f1 into remotion-dev:main Feb 13, 2026
13 checks passed
@acj acj deleted the handle-empty-lambda-payload branch February 13, 2026 11:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments