After Upgrading Remotion, Renders Failing More Often

[brave needle]

After upgrading from Remotion 4.0.372 to 4.0.417, Lambda renders are failing with download timeouts. The same videos load instantly in a browser.

    at Timeout.<anonymous> (/var/task/index.js:92:753)
    at listOnTimeout (node:internal/timers:605:17)
    at process.processTimers (node:internal/timers:541:7)

[Tab 0, src/components/timeline/canvas/items/video-item.tsx:80] OffthreadVideo has an error: Error: Tried to download file https://media.viewmax.io/users/xxx/assets/xxx.mp4, but the server sent no data for 20 seconds```


Also getting this error:

ERROR Could not extract frame from compositor Error: Received a status code of 522 while downloading file https://media.viewmax.io/users/xxx/assets/xxx.mp4.
The response body was:

error code: 522

at $fe (/var/task/index.js:91:13872)

This error affects multiple chunks in parallel renders (e.g., chunks 23 and 30 timeout while others succeed). The weird thing is after a few hours if the user exports again it will work fine.

For context, videos are hosted on Cloudflare R2, accessed via custom domain.

Any advice on how we can debug this?

[brave needle]

in the lambda failed invocations tab I'm seeing:

TimeoutNegativeWarning: -2168 is a negative number. Timeout duration was set to 1.

and

[chrome] net/disk_cache/simple/simple_index_file.cc:323: Could not obtain information about cache age
[chrome] net/disk_cache/simple/simple_index_file.cc:330: Failed to write the temporary index file

progress.json doesn't seem to help since it doesn't show any errors. but the video render is not completed. you can see:
"framesRendered": 554,
"framesEncoded": 474,
"durationInFrames": 634

so like smt is messing up

[spring quartz]

if you get a 522, that is from your side
https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/

thanks for letting me know about TimeoutNegativeWarning.
this is something because we upgraded to nodejs 24, before it was probably silent

[earnest remnant]

Filed an issue "Error messages related to negative timeout values and Chrome cache issues.": https://github.com/remotion-dev/remotion/issues/6465. Please follow the issue for when we fix it!

[brave needle]

thanks!

cant believe I didn't check the docs there 🤦

[rain ledge]

hi @brave needle , we're getting the same error and also store some media on R2.

we also saw this after upgrading remotion recently, from .408-.421 (latest)

our error is the but the server sent no data for 20 seconds

what did you do to resolve it?

[brave needle]

Havent resolved yet unfortunately

[spring quartz]

I've also gotten this one fetching from cloudflare
still unclear to me if this is a bug or unintentional throttling from cloudflare's side 🤔 and what we can do about it

[brave needle]

yeah its really hard to reproduce this bug sometimes as well, and this issue only happens on lambda, never on player, so it makes me think it might be some sort of throttling but I'm not sure.

[rain ledge]

Seems like it only occurred when we upgraded from .408 to .410, then we downgraded back and the problems didn’t appear

i think it is a cloudflare issue for sure but also unsure why it (seems) to be occurring only in newer versions