[user-github-me]

Long videos can still spend too much time in Lambda planning when their sources cannot defer extraction to chunk workers. Document how to identify the failed phase, configure the deployed function, and split jobs that exceed an invocation's time or temporary-storage budget.

The guidance now matches current main: ordinary CFR and VFR extraction runs in segments of up to two minutes, and FFMPEG_PROCESS_TIMEOUT_MS limits time without a new frame rather than total extraction time. It also distinguishes eligible Plan v2 deferral from extraction that still occurs during Plan, preserves the current byte-range input reads, and identifies the arm64 video function used by default deployments. This incorporates the earlier review request and the subsequent extraction changes in #5921, which supersede the old VFR-only deadline advice.

Validation: current implementation traced for extraction, stall detection, Lambda routing, and CDK configuration; 27 existing FFmpeg process tests passed; full workspace build, Mint validation/link checks, normal commit hooks, and both comment checks passed. No AWS deployment was performed.

The timeout example now identifies render as the HyperframesRenderStack instance created in the CDK example above. This prose-only follow-up passed documentation validation, broken-link checks, normal commit hooks and both comment checks.

[jrusso1020]

Thanks for writing this up. Several parts are accurate and useful:

• the Plan step description;
• the point that smaller chunks don't reduce Plan's extraction work;
• setting the variable on the deployed function rather than in the local shell;
• splitting oversized jobs.

However, #5280 changes extraction so that ranges longer than two minutes run as two-minute segments, each with its own process timeout, and it adds a bullet in the same place under Current limits. Once it lands, the troubleshooting text saying the 300,000 ms timeout covers the whole extraction, and the advice to raise it for long clips, will be out of date. That advice still applies to variable-frame-rate sources, which are extracted in one pass.

Could you rebase after #5280 merges, reword the timeout guidance for per-segment timeouts (scoped to the variable-frame-rate case), and fold your Current limits bullet into the one #5280 adds?

— Rames

[jrusso1020]

Thanks for this, @user-github-me. This PR now has merge conflicts with main. Could you rebase it onto the latest main? Once it's conflict-free we'll review it and get it into the merge queue.

[mintlify]

Preview approval required

This pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit 24a9ba2.

Approve preview

[miguel-heygen]

Thanks for the rebase and the rework. I checked the new text against current main, and it holds up:

• ffmpeg_timeout is now a no-new-frame timer (videoFrameExtractor.ts, the inactivity branch that reports "no new frame for N ms"), so "frame progress resets that timer" is right.
• Extraction runs in segments of up to 120 seconds, including VFR sources.
• Plan v2's deferral skips VFR sources and HDR conversions and probes the last second of the source, which matches "after a short timing probe".
• HyperframesRenderStack exposes renderFunction, so the CDK snippet works.

The earlier asks are covered: the timeout advice is about stalls rather than total time, and there's one Current limits bullet instead of two.

One optional nit: the snippet's render isn't defined anywhere. A comment such as // render = new HyperframesRenderStack(app, "Render", …) would save readers a lookup.

Reviewed head 16b6238a. It merges cleanly with main, and the docs checks are green.

Verdict: APPROVE
Reasoning: A docs-only change whose technical claims all match current main; the earlier change requests are addressed and CI is green.

[miguel-heygen]

Thanks for picking up the nit. The new sentence points at the right thing: the CDK example above creates render as the HyperframesRenderStack instance. Nothing else changed since my last review, so that approval stands at this head.

Reviewed head 24a9ba2d. Docs checks are green.

Verdict: APPROVE
Reasoning: The only change since the last approval is a one-sentence clarification that matches the CDK example in the same page.