What does `Error saving state.` mean?

We’re seeing Error saving state. messages in our logs:

{
  "date": "2026-04-27T01:03:43.300Z",
  "type": "f",
  "description": "Error saving state.",
  "connection_id": "",
  "client_id": "...",
  "client_name": "...",
  "ip": "...",
  "user_agent": "Edge 147.0.0 / Windows 10.0.0",
  "details": {
    "body": {},
    "qs": {
      "client_id": "...",
      "response_type": "token id_token",
      "redirect_uri": "...",
      "scope": "openid profile",
      "audience": "backend",
      "state": "****************************wpUL",
      "nonce": "...",
      "auth0Client": "eyJuYW1lIjoiYXV0aDAuanMiLCJ2ZXJzaW9uIjoiOS4zMC4xIn0="
    },
    "error": {
      "message": "Error saving state.",
      "oauthError": "server_error",
      "type": "oauth-authorization"
    },
    "session_id": "...",
    "riskAssessment": null
  },
  "hostname": "...",
  "audience": "backend",
  "scope": "openid profile",
  "auth0_client": {
    "name": "auth0.js",
    "version": "9.30.1"
  },
  "$event_schema": {
    "version": "1.0.0"
  },
  "environment_name": "prod-us-1",
  "log_id": "...",
  "tenant_name": "...",
  "_id": "...",
  "isMobile": false,
  "location_info": {},
  "id": "..."
}

context:

{
  "body": {},
  "qs": {
    "client_id": "...",
    "response_type": "token id_token",
    "redirect_uri": "...",
    "scope": "openid profile",
    "audience": "backend",
    "state": "****************************wpUL",
    "nonce": "...",
    "auth0Client": "eyJuYW1lIjoiYXV0aDAuanMiLCJ2ZXJzaW9uIjoiOS4zMC4xIn0="
  },
  "error": {
    "message": "Error saving state.",
    "oauthError": "server_error",
    "type": "oauth-authorization"
  },
  "session_id": "...",
  "riskAssessment": null
}

What state is it trying to save where? Why isn’t it succeeding? Who’s responsible for this?

Hi @jsoref

Thank you for reaching out to us!

Based on the information provided, the server_error message that you are seeing in your tenant’s logs could indicate a server-side problem, which likely lies within the Auth0 platform. I recommend running some checks for any potential causes:

  • any Actions that you have configured for the login flow could contain a misconfiguration that would throw this error. Please review any custom code that you may have running;
  • verify that tenant settings are correct, such as Connection and Authorization settings.

In addition to the above, please let us know any additional details on the behaviour that you are seeing, if it’s limited to some users, group of users, application etc.

Best regards,
Gerald