Troubleshooting

Start with the message shown in the build’s attention block. It normally identifies whether the problem belongs to a provider account, the generated work, the preview, or delivery.

Quick diagnosis

Symptom	Check first	Action
Build failed or stopped	Attention block and latest activity	Fix the named issue, then use Doctor
Workspace sessions need attention	Settings → Workspace & more	Refresh once, then choose Repair workspace if it remains stuck
Old sessions can be cleaned up	Workspace health card	Choose Sweep stale sessions; active builds are preserved
Credential error	The provider’s Test in Settings	Reconnect or replace the failed credential
Preview does not load	Whether the final pass just finished	Wait briefly, then reload; idle servers may need to wake
Media build will not start	Required media provider in Settings	Connect and test the matching provider
One story is stuck	Story status and worker activity	Swap that story to another connected agent
Artifact is missing	Selected output and delivery status	Confirm the artifact was requested, then run Doctor

The build failed

Open the build and read the attention block. Then use Doctor to diagnose the failure again and resume. A missing or expired provider key is a common cause, so fix it in Settings and use Test before trying again.

Workspace sessions need attention

LoopCodeLab runs sign-ins, builders, reviewers, and delivery steps in isolated workspace sessions. If that session service becomes stuck, a new agent may be unable to start even though your project files are fine.

You will see Workspace sessions need attention or an attention message explaining that no agent work started. Use this recovery order:

1. Open Settings → Workspace & more and choose Refresh status once.
2. If the status becomes Idle, no sessions are running and nothing is wrong. The service starts automatically when the next agent begins.
3. If the status is Cleanup available, choose Sweep stale sessions. This removes expired sign-in sessions and completed build sessions while preserving active builds and project files.
4. If the status remains Repair required, choose Repair workspace. On an affected build you can instead choose Repair workspace & retry.
5. Read the confirmation before continuing. Repair closes open terminal tabs and restarts only your workspace session service. It does not delete project files or completed agent work.

Repair is blocked while an agent, reviewer, or final integration pass is still active. Pause the build and allow active work to drain, or wait for it to finish, then try again.

After a successful repair, newly detected session-start failures are queued again automatically. An older build that failed before this recovery feature may remain marked Failed even though the workspace is repaired. In that case, choose Doctor once to reset its failed story and dependency-blocked stories. Do not run Repair repeatedly.

Workspace status meanings

Status	Meaning	What to do
Healthy	Active workspace sessions are responding	Nothing
Cleanup available	Managed sessions have passed their safe age limit	Sweep stale sessions
Repair required	The session service cannot reliably start or inspect work	Refresh once, then repair
Idle	No workspace session service is running	Nothing; it starts when needed

The preview does not load

Give the preview a moment after the final pass. Server-type apps can stop while idle and restart on the next visit.

A media build will not start

Connect the matching media provider key in Settings first. Media generation cannot start without its provider credential.

I see a credential error

Open Settings and use Test on the provider credential. The result tells you which key or sign-in needs attention.

Before asking for help

Keep the build name, approximate failure time, attention message, diagnostic code, and failed provider or story ready. Do not send API keys, access tokens, or private signing files.