[richiemcilroy]

Loom import workflows used to poll the database every 5 to 30 seconds until their media job finished. Each poll is a workflow step plus a replay on Vercel, so a ten minute import cost about 25 invocations, and a batch of 1,200 imports cost tens of thousands.

Now each processing attempt creates a workflow hook whose token goes into the worker's webhook URL. When the worker reports complete, error or cancelled, the progress route saves the state first and then resumes the hook. The workflow then reads the status once. A typical import now uses two status reads instead of dozens.

Safety nets:

• If the signal is lost, the workflow still checks every 5 minutes, within the same 1 hour limit.
• If the signal arrives before the saved state is visible, it falls back to the old short polling.
• Tokens only resume hooks that belong to the same video. Unknown or disposed tokens are ignored.
• Each hook is disposed when its attempt ends.
• Runs already in flight stay on the deployment that started them.

Recording, instant and web uploads still use waitForVideoProcessing and are unchanged.

Stacked on #3118.

Tests: video-processing-status 15, media-server-progress 59, media-processing-workflows 27 pass. The 7 share-stage-identity failures also fail on main.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking gap in tests for the new signal helper.

Findings

1.  Signal checks lack direct tests ▶

Fix with agent prompt

### Issue 1
apps/web/__tests__/unit/media-server-progress.test.ts:79-81
These tests replace `signalLoomImportFinished` entirely, so broken token checks or error branches would still pass. Add focused tests that mock `resumeHook` instead: missing and wrong-video tokens must not resume anything, matching tokens must pass the phase, and missing hooks and other errors must not escape. This would cover the promised behavior for stale worker callbacks.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Loom imports now wait for worker callbacks instead of frequent database checks.

• Loom imports wake when their media worker finishes.

_{Reviews (1) · Last reviewed commit: "perf: wake Loom import workflows from th..." · Reviewed by Greptile}

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated
cap-status	Skipped		Oct 24, 2026 4:52pm UTC

[richiemcilroy]

@greptileai

[greptile-apps]

Signal checks lack direct tests

These tests replace signalLoomImportFinished entirely, so broken token checks or error branches would still pass. Add focused tests that mock resumeHook instead: missing and wrong-video tokens must not resume anything, matching tokens must pass the phase, and missing hooks and other errors must not escape. This would cover the promised behavior for stale worker callbacks.

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/web/__tests__/unit/media-server-progress.test.ts
Line: 79-81

Comment:
**Signal checks lack direct tests**

These tests replace `signalLoomImportFinished` entirely, so broken token checks or error branches would still pass. Add focused tests that mock `resumeHook` instead: missing and wrong-video tokens must not resume anything, matching tokens must pass the phase, and missing hooks and other errors must not escape. This would cover the promised behavior for stale worker callbacks.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!