[yashranaway]

a loom import started from the mobile app handled failures badly. if the import workflow failed to start the video sat on "importing from loom" with no failure recorded, and any retry with that link got a 400 because the stuck one counted as already imported, at least until the recovery cron picked it up. storage or restart failures also came back as 400, so the app told people the video might be private when it was a server problem. the same link would just restart on the web.

the mobile route had its own copy of the import flow without the web's recovery. now it keeps its own url, pro, org and rate limit checks and calls the same import helper the web and csv imports use, so failed imports restart and start failures get recorded, and server side failures return 500 while real client errors stay 400. that also drops about 100 duplicated lines. the new test is added to the ci list.

Confidence Score: 5/5

The PR appears safe to merge; no new actionable issues remain.

Summary

Mobile Loom imports now use the shared import helper, which records startup failures and lets users restart failed imports.

• Mobile Loom imports use the shared flow and can restart eligible failures.

_{Reviews (3) · Last reviewed commit: "fix(web): report Loom startup failures a..." · Reviewed by Greptile}

[vercel]

@yashranaway is attempting to deploy a commit to the Cap Software Inc Team on Vercel.

A member of the Team first needs to authorize it.

[yashranaway]

@greptileai review

[yashranaway]

@greptileai review