portal_changed - Unkey Docs

err:unkey:data:portal_changed

portal.createSession was working out the session’s access from the portal’s app or keyspace when the portal was pointed somewhere else. The session was not created, because it would have carried access to the old app or keyspace. You get HTTP 409.

Example response

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "The portal changed while the session was being created. Try again.",
    "status": 409,
    "title": "Conflicting Resource",
    "type": "/errors/unkey/data/portal_changed"
  }
}

Likely causes

Someone called portal.updatePortal with a new keyspaceId or appId at the same moment you called portal.createSession.

How to fix

Retry portal.createSession. The new session uses the portal’s current app or keyspace.

Last modified on October 6, 2026

⌘I