Skip to content

fix(generation): wait up to 30 minutes for a lost generation to save - #185

Merged
Nhaaa4 merged 1 commit into
mainfrom
fix/long-generation-wait
Oct 21, 2026
Merged

Nhaaa4 merged 1 commit into
mainfrom
fix/long-generation-wait

Conversation

@PromSereyreaksa

Copy link
Copy Markdown
Member

Why

Backend PR COPPSARY/Motify-Backend#80 makes the agent write films that are too long for one model response (e.g. remaking 6–7 attached slides) in parts instead of failing. Those runs can take ~20 minutes.

BACKGROUND_WAIT_MS — the fallback that waits for a saved film after the editor loses track of a job (connection drop, backend restart) — was 10 minutes, so it could give up and show a failure while the backend was still finishing. Raised to 30 minutes to match the backend's RUN_LEASE_TTL_MS.

Job polling in runMotionMessage has no overall deadline, and MAX_PROMPT_IMAGES is already 10 to match the backend, so nothing else changes.

Testing

  • tests/ui/background-generation.test.ts and src/cloud/projects-api.test.ts pass (27 tests).

A film too long for one model response is now written in parts on the
backend and can take about twenty minutes. The 10-minute fallback wait
could give up and report a failure while the backend was still working.
Matches the backend's RUN_LEASE_TTL_MS.
@vercel

vercel Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
motionly Ready Ready Preview Oct 21, 2026 12:06pm UTC

Request Review

@Nhaaa4
Nhaaa4 merged commit a7ee4be into main Oct 21, 2026
8 checks passed

This branch was successfully deployed

1 active deployment
Preview — ee8af0bf Deployed Oct 21, 2026 by vercel[bot]
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