Unity
Troubleshooting
Every message the package prints in the Unity Console starts with [PERSONAIZER]. Find yours below. Session start failures also name the error code in brackets, such as [auth.not_owner], followed by what the server said; the full code list is on Errors & limits.
Setup
No API key
[PERSONAIZER] No API key. Add your account API key in Project Settings → PERSONAIZER, or switch to Server Token mode.
The mode is API Key and the key field is empty. Copy your key from Profile → API access in the dashboard, paste it in Project Settings → PERSONAIZER and press Connect. To keep the key out of your build, use Server Token mode instead.
Persona ID is empty
[PERSONAIZER] Persona ID is empty. Copy it from the dashboard: Persona → API.
The Persona Character has no Persona ID. Copy it from your persona's API tab in the dashboard into the component's Persona ID field.
Persona ID is not valid
[PERSONAIZER] Persona ID is not valid. It looks like d99f64dd-0acb-…; copy it from the dashboard: Persona → API. The account API key (ak_…) goes in Project Settings.
The field holds something other than a Persona ID, most often the account API key. Persona IDs look like d99f64dd-0acb-…; the ak_… key goes in Project Settings.
Persona not found
[PERSONAIZER] Session start failed (…) [resource.not_found]: Persona not found. Check the Persona ID (dashboard: Persona → API).
No persona has this ID: it was mistyped, or the persona was deleted. Copy the ID again from the persona's API tab. See resource.not_found.
Can't reach the server
[PERSONAIZER] Session start failed (0): Can't reach the server. Check the internet connection.
The request never got an answer. Check the machine's internet connection, and any firewall or proxy between the game and *.personaizer.com.
Server is at capacity
[PERSONAIZER] Server is at capacity; queued sessions are not supported yet.
PERSONAIZER is busy and offered a place in its waiting queue, which the package doesn't join. Try again in a moment.
Authentication
API key invalid or rotated
[PERSONAIZER] Session start failed (…) [auth.api_key_invalid]: The API key is invalid or was rotated. Update it in Project Settings → PERSONAIZER.
The key doesn't match your account's current key: it was mistyped, or rotated on your profile since. Copy the current key from Profile → API access, paste it in Project Settings and press Connect. Builds made with the old key stop working until you ship one with the new key. See auth.api_key_invalid.
API key disabled
[PERSONAIZER] Session start failed (…) [auth.api_key_disabled]: The API key is disabled. Check Profile → API access in the dashboard.
The key exists but is turned off. Turn it back on, or create a new one, on Profile → API access. See auth.api_key_disabled.
Account doesn't own this persona
[PERSONAIZER] Session start failed (…) [auth.not_owner]: The API key's account doesn't own this persona. Use a Persona ID from the same account.
The API key and the Persona ID belong to different accounts. Use a persona from the key's account, or the key of the account that owns the persona. See auth.not_owner.
Identity token invalid
[PERSONAIZER] Session start failed (…) [auth.identity_token_invalid]: Your server's token was rejected. Sign it (HS256) with your account's Identity Secret, include a sub claim, and expire it within 10 minutes.
Server Token mode only. The token your server returned failed verification: signed with the wrong secret (or an old one, after a rotation), not HS256, no sub claim, or an exp more than 10 minutes ahead. Check it against the identity token format. See auth.identity_token_invalid.
Identity token expired
[PERSONAIZER] Session start failed (…) [auth.identity_token_expired]: Your server's token expired. Return a fresh token for every request.
Server Token mode only. The token's exp had passed, beyond the 1 minute of allowed clock skew. Sign a new token for every request instead of caching one, and check your server's clock. See auth.identity_token_expired.
No credentials sent
[PERSONAIZER] Session start failed (…) [auth.origin_not_allowed]: No credentials were sent. Set an API key or a Server Token endpoint in Project Settings → PERSONAIZER.
The session request carried neither an API key nor a token, so PERSONAIZER treated it as a web page from an unlisted domain. Set a key or a Token Endpoint in Project Settings → PERSONAIZER, or set PersonaAuth.TokenProvider in code. See auth.origin_not_allowed.
Server Token
No token endpoint
[PERSONAIZER] No token endpoint. Add your server's URL in Project Settings → PERSONAIZER, or set PersonaAuth.TokenProvider in code.
The mode is Server Token, the Token Endpoint field is empty, and no PersonaAuth.TokenProvider is set. Add your token server's URL, or set a provider in code.
Token endpoint unreachable
[PERSONAIZER] Token endpoint https://game.example.com/personaizer-token answered 0 Cannot connect to destination host. Check that your token server is running and reachable.
Your token server didn't answer 200. The number after "answered" is the status it gave, or 0 when it couldn't be reached at all. Check that the server is running, the URL in Project Settings is right, and the route accepts POST with a JSON body. On WebGL, the server must also allow your game's origin (CORS).
Token endpoint returned no token
[PERSONAIZER] Token endpoint https://game.example.com/personaizer-token returned no "token" field.
Your server answered 200, but the body had no token. It must be JSON shaped {"token": "<identity token>"}. See Server Token mode.
TokenProvider failed
[PERSONAIZER] PersonaAuth.TokenProvider failed: <your exception's message>
The function you set as PersonaAuth.TokenProvider threw. The text after the colon is your exception's message; fix it in your own code.
TokenProvider returned no token
[PERSONAIZER] PersonaAuth.TokenProvider returned no token.
Your PersonaAuth.TokenProvider returned null or an empty string. Return the token string your backend signed.
Plan limits
Your plan's current usage is under Project Settings → PERSONAIZER → Usage in API Key mode, and in the dashboard in either mode. The rules behind each limit are on Usage & limits.
Credits used up
[PERSONAIZER] Session start failed (…) [limits.credits_exhausted]: Your plan's credits are used up. See Project Settings → PERSONAIZER → Usage, or upgrade your plan.
This billing cycle's credits are spent, so no new conversation can start. Upgrade the plan, or wait for the cycle to reset. See limits.credits_exhausted.
Subscription required
[PERSONAIZER] Session start failed (…) [limits.subscription_required]: This needs an active subscription. Check your plan in the dashboard.
The account has no active subscription. Choose a plan in the dashboard. See limits.subscription_required.
Too many conversations at once
[PERSONAIZER] Session start failed (…) [limits.concurrent_session]: Your plan's limit of conversations at the same time is reached. End another conversation first, or upgrade your plan.
Your plan caps how many conversations can be connected at the same time, across every player and the Editor. End one (call Disconnect(), or destroy its Persona Character), or upgrade. See limits.concurrent_session.
PERSONAIZER at capacity
[PERSONAIZER] Session start failed (…) [limits.waiting_room_full]: PERSONAIZER is at capacity right now. Try again shortly.
PERSONAIZER can't take more conversations right now. Nothing is wrong with your setup; try again shortly. See limits.waiting_room_full.
Too many session starts
[PERSONAIZER] Session start failed (…) [limits.rate_exceeded]: Too many session starts in a short time. Try again in a moment.
The game started sessions faster than the rate limit allows, often a script that calls Connect() in a loop or on every frame. Connect once and keep the session. See limits.rate_exceeded.
Session closed
These arrive during a conversation, when PERSONAIZER closes it. The Persona Character's state becomes Failed. Each close code is listed on Errors & limits → Close codes.
4003: closed by the plan
[PERSONAIZER] Disconnected: Conversation ended by the plan's limits. Please upgrade your plan. (SessionPlanLimitReached) …
The account lost its active subscription, or its plan's limit of conversations at once was lowered while this one was running. Check the plan in the dashboard. See close 4003.
4005: per-session credit cap
[PERSONAIZER] Disconnected: Session limit reached. (SessionInteractionLimit) …
The conversation reached the credit cap set on this persona for a single session. Starting a new conversation is allowed. To raise the cap, change the persona's session limits in the dashboard. See close 4005.
4006: per-session duration cap
[PERSONAIZER] Disconnected: Session limit reached. (SessionDurationLimit) …
The conversation reached the duration cap set on this persona for a single session; idle time counts. Starting a new conversation is allowed. To raise the cap, change the persona's session limits in the dashboard. See close 4006.
4007: credits used up
[PERSONAIZER] Disconnected: This plan's credits are used up. Please upgrade your plan. (SessionCreditsExhausted) …
The plan's credits ran out during the conversation. Upgrade the plan, or wait for the cycle to reset. See close 4007.