Troubleshooting

Find the message or symptom you are seeing, then follow the fix. If nothing here helps, email support@prophouse.dev with your workspace name, the desktop app version (shown in the title bar menu), and what you expected versus what happened.

Sign-in problems

I can’t sign in after creating my account

New accounts must verify their email first. Look for the verification email sent when you signed up (check your spam folder too) and select its link. If you can’t find it, email support@prophouse.dev. If you forgot your password, use Forgot password on the sign-in page.

“Sign in with browser” doesn’t finish

The desktop app and Unreal plugin sign in by opening an approval page in your browser. If the app keeps waiting:

1. Make sure you are signed in to https://app.prophouse.dev in that browser.
2. If no browser tab opened, go to https://app.prophouse.dev/device and type the code the app is showing.
3. Check that the code on the page matches the code in the app, then select Approve sign-in.

Codes expire after 15 minutes. If the page says That code isn't waiting for approval — it may have expired or been mistyped. Ask the app for a fresh one., start the sign-in again from the app. If you selected Deny by mistake, start again too.

The desktop app shows a “Connect” screen or can’t reach the server

The desktop app connects to https://api.prophouse.dev by default. If it was pointed somewhere else, select Connect to a different server… on the sign-in screen, set Server URL to https://api.prophouse.dev, and select Connect.

The plugin says “Session expired — sign in again.”

The key the plugin was using no longer works, for example because it was revoked on API keys. Open Window → Prophouse and select Sign in with browser.

Errors from a key or token

Message	Cause and fix
Unknown or revoked API key.	The key was revoked or mistyped. Create a new one on API keys, or sign the app in again with Sign in with browser.
The account that created this API key is no longer a member of this workspace.	Keys stop working when their creator leaves. An admin needs to issue a new key.
This key is read-only. Use a write-scoped key…	You tried to change something with a read key. Use a write key or sign in from the app, which requests write.
Your membership in this workspace is no longer active. Sign in again.	Your account is no longer a member of the workspace. Sign in again; if you were removed, ask an admin to invite you back.
This account already belongs to a workspace — one workspace per account.	Each account can belong to one workspace. Accept the invite with a different account.

See API keys for scopes and revocation.

Agent imports into Unreal fail

When an AI agent’s import_to_unreal call fails, the error code says what to fix. The common ones:

Code	Fix
UNREAL_EDITOR_OFFLINE	Open the project in Unreal with the Prophouse plugin signed in as the same account the agent uses, then retry.
AGENT_IMPORTS_DISABLED	In that editor, turn on Editor Preferences → Plugins → Prophouse → Agent imports → Accept agent imports. It is off by default.
DESKTOP_AGENT_UNAVAILABLE	Install or start the Prophouse desktop app on the same machine as the editor.

The full list, including UNREAL_NOT_CONNECTED and UNREAL_PROJECT_AMBIGUOUS, is in Import props into Unreal.

Pushes or pulls in Unreal don’t start

The Unreal plugin hands every upload and download to the Prophouse desktop app, so transfers keep going if you close the editor. If the desktop app is not installed, the editor shows Prophouse agent required with an Install the Prophouse desktop app link. Install it from prophouse.dev/download, sign in, and try again. If it is installed but not running, start it.

429 errors and rate limiting

A REST API request that returns 429 with Rate limit exceeded for this key. Back off and retry. means a single key sent too many requests in a short window. The response includes a Retry-After header (in seconds). Wait that long, then retry, and slow down any loop that is making calls. Large push, pull and sync transfers use a separate, higher limit, so normal library transfers do not trip it.

AI agents calling tools over MCP see these limits as tool errors (isError: true) rather than a failed connection, each with retryable: true, details.retry_after_seconds and a Retry-After header:

• RATE_LIMITED: the key went over the same per-key rate limit. Wait retry_after_seconds, then retry more slowly.
• AGENT_CALL_LIMIT: the workspace used its monthly allowance of MCP tool calls. retry_after_seconds counts down to the start of the next month (UTC), and details.used and details.limit show the count. Retrying will not help before then. Searching from the apps and the editor still works. To raise the ceiling, add seats or change plan; see Plans and limits.

A JSON-RPC batch sent to MCP still gets a plain 429 for either limit. See Errors and limits for the full shapes.

The desktop app isn’t updating

The desktop app checks for updates automatically. To check by hand:

1. Open Settings and find the About card.
2. Select Check for updates. If a new version is available, select Download update, then Restart to update.

If you see Could not reach the update server. Try again in a moment., check your network connection and try again. If updates still fail, download the latest installer from prophouse.dev/download and run it.

Search results look keyword-only

Natural-language search ranks props by meaning and appearance as well as by keywords. If results only match words in names, packs, categories, tags and comments (for example, a description finds nothing unless it contains a prop’s name), semantic search may be temporarily degraded. When that happens, search falls back to keyword matching so you still get results. Search by image and similar-prop browsing may also be unavailable during that time.

A prop that was pushed very recently may also match only by keyword until it has been indexed. Try again in a few minutes.

Other errors

Message	Cause and fix
Library is being prepared — try again in a minute.	Your library is starting up or being set up. Retry shortly.
Library temporarily unavailable — retry shortly.	A temporary problem reaching your library. Retry after a few seconds.
Workspace suspended. Fix billing at app.prophouse.dev/billing. (402)	A payment failed and the grace period ended. Fix the card through Manage billing on Billing. Nothing has been deleted.
A push is refused because the prop is locked	A teammate has the prop checked out. The error names them. Wait for them to release the lock, or ask them to. See Collaboration.

Tip

On the Free plan, pushes stop at the 50 GB cap while search and downloads keep working. On paid plans, pushes pause at your storage limit, which you can raise on Billing.