Troubleshooting and getting support
Start with the project route, the current run or deployment state, and the most recent error. Avoid unrelated changes while one failure is unresolved.
Agent run is waiting or failed
If the status is awaiting input, answer the displayed question or approval request; do not assume the model should restart automatically. If the run failed, open the final failure event and preserve the exact evidence. Resume or retry only through the action offered by the project after you understand what will continue.
Preview does not open
Check the Runtime panel for process readiness and logs. Then confirm the preview is using the latest checkpoint, the expected device/route is selected, and required environment values exist. Distinguish process startup failure from application, API, and browser errors. Do not repeatedly rebuild a project while the same root cause remains.
Build, test, or publication failed
Read the first actionable error from the relevant job or test result. Confirm the project type and action are compatible: Web publication is not a Native store build, and a Design prototype is not a hosted app. Fix the failing step and verify that same step before proceeding.
Access or billing problem
Confirm the active account, organization, membership role, and billing context. For an invitation, use the intended account. For a payment, inspect the order or invoice status before retrying. Ask an organization administrator to review policy or entitlement errors.
Contact support
Provide the page or project route, project identifier, run/build/deployment identifier, approximate time, expected and observed behavior, and a short reproduction sequence. Include screenshots or sanitized logs when useful. Remove passwords, API keys, personal data, and private invite tokens before sharing.