I'm running into a recurring Failed to acquire lock for vm:{id}:files-sync error in v0.app. This has happened multiple times across different chats/projects over the past few weeks, always in the same pattern:

Pattern:

• The agent is mid-way through a multi-step task list (usually 3-5 steps), actively editing files.
• Right before the lock error, there's typically a heavier file operation — a production build (Built project → Build finished), a large batch of file edits, or several sequential tool calls (typecheck, lint, read files, edit files) without pause.
• The agent then either:
  • Shows repeated Retried sandbox check / Checked sandbox health attempts that don't resolve, and the task sits paused for 5-10+ minutes with no progress, or
  • Surfaces the explicit Failed to acquire lock for vm:{id}:files-sync error.

What I've tried (partial workarounds):

• Hard refresh (F5) on the page — sometimes forces reconnection and the sandbox recovers (Reconnected to preview, Switched version appear in logs afterward).
• Waiting several minutes without sending "continue" — sending "continue" repeatedly while locked seems to make it worse, possibly queuing more conflicting file-sync attempts on the same VM.
• Breaking large multi-task prompts into single-task prompts — reduces frequency but doesn't eliminate it, especially when a task involves a build step.

Impact:

• Lost time waiting for the sandbox to recover.
• Burned credits on tasks that stall mid-execution (agent keeps "thinking"/retrying while the VM is unresponsive).
• Not consistently reproducible on demand, which makes it hard to pin down — but frequent enough to disrupt normal multi-step agent workflows.

Ask: Is this a known issue on the infra/sandbox side? I found a couple of older threads describing similar symptoms (vm:files_sync ... blocking login, Unable to acquire lock at .next/dev/lock), so it doesn't seem isolated to my account/project. Any guidance on avoiding it, or an ETA on a fix, would be appreciated.

I'm happy to share screenshots/logs of specific occurrences if that helps debug.