Troubleshooting

This page covers the most common issues builders run into. If your problem is not here, check contacting support.

Verification email did not arrive — check spam, then resend from the sign-in page. If it still does not arrive after 5 minutes, the email may be blocked by your domain. Try a different email or contact support.
Forgot password — click Forgot password on the sign-in page. Reset link arrives by email.
OAuth provider error — if Google or GitHub sign-in fails, try the email/password flow instead. Check that the OAuth account uses an email already registered with Archie.
Locked out — too many failed attempts trigger a temporary lockout. Wait 15 minutes or contact support.

My build failed

Open Project → Activity and find the build entry. The error message points to which agent failed and why. Common causes:

Insufficient credits — check Plans and credits. Top up or upgrade.
Blueprint inconsistencies — a module references a service that does not exist, or a user type with no permissions. Open the blueprint and resolve the warnings before re-running.
Conflicting hand edits — if you edited code outside Archie and the build cannot reconcile, the build error names the conflict. Resolve in the IDE, then re-run.

For repeated build failures with no obvious cause, contact support with the project ID and the build log.

404 on the deployed URL — the deployment may not have finished. Wait 1–2 minutes after a deploy, then refresh.
Custom domain not working — DNS records may not have propagated. Verify in project settings. Propagation can take up to 48 hours.
Recent change broke something — roll back to a previous deployment from the deployment history. See deployment.

Migration did not apply — check Backend → Environments. If the migration is pending, run it manually. See environments.
Wrong environment — confirm you are looking at production data, not preview or staging. The environment switcher is in the project nav.
RLS or permissions — if a user cannot see data they should, check role-based access.

Click Start inspecting first.
Server-only or background elements (computed in middleware, hydrated late) may not be inspectable. Edit those in the IDE.
Hard-refresh the preview to reload the inspector bridge.

API keys are scoped per environment. Check that the key was generated in the environment you are calling.
Confirm you are sending the key as a Bearer token: Authorization: Bearer <key>.
See API keys for the full troubleshooting flow.

If none of the above resolves your issue, contact support with: account email, project ID, what you expected, what happened, and reproduction steps.