Runtime diagnostics
Classify failures by request, generation, artifact loading, runtime dependencies, and publication before retrying.
On this page
Request admission and context
First establish whether the request was sent and accepted. A composer error can indicate missing attachments, oversized context, authentication, a usage limit, or an active run. Correct that condition before investigating generated code. For expired sign-in or an email-code flow, follow the actual sign-in screen rather than assuming a particular provider is enabled.
Artifact loading versus application failure
Open the preview separately and inspect Console and Network in browser DevTools. Record the failing URL without secrets, HTTP status, response type, visible message, and whether the document, an asset, or a service request failed. A 200 response for HTML does not establish that JavaScript initialized or data requests succeeded.
Use Reload preview or the offered recovery action for a loading failure. For a runtime defect, reproduce the smallest interaction sequence and send that evidence with the relevant version. If the external export works visually but authentication or service calls fail, inspect missing host-side routing before rewriting UI code.
Interrupted generation
Read the last run state and use its specific action: Try reconnecting, Resume build, or Try again when offered. They are not interchangeable. Before starting a duplicate request, verify whether an artifact was saved or the prior run recovered. A disconnected client does not prove that a provider operation was cancelled.
Publication and ownership
Compare the preview version with the public version. Ordinary edits require a new Publish action. If publication reports missing owner access, reopen the original conversation/browser as directed. Clearing local storage can remove useful project context and should not be a default diagnostic step.
Credential, origin, and quota failures
Check the live connector state, the project's key status, and the provider response. Distinguish an unavailable integration, a disconnected account, a missing or rejected key, an origin/session mismatch, and an exhausted quota. Use the app's displayed message and response details; an HTTP status alone does not identify the root cause.
Provide a diagnostic bundle
Project/conversation URL and tested version:
Time and timezone:
Browser/device and signed-in state:
Minimal reproduction:
Expected versus actual result:
Failed request status or console message (redacted):
Whether it reproduces in preview, public site, or exported project:
Recovery actions already attempted: