500 errors on API V2 after migration to Zitadel v4

Hi Zitadel community

We had a Zitadel instance in v2.67.2 that we gradually migrated to v4.2.0. Some queries to the V2 API now return 500 errors, for example:

Call to /v2/users

Request body :
{
  "query": {
    "offset": "0",
    "limit": 100,
    "asc": true
  },
  "sortingColumn": "USER_FIELD_NAME_EMAIL",
  "queries": [
    {
      "inUserIdsQuery": {
        "userIds": [
          "337531633278126348"
        ]
      }
    }
  ]
}

500 Response :
{
    "code": 13,
    "message": "An internal error occurred (QUERY-AG4gs)",
    "details": [
        {
            "@type": "type.googleapis.com/zitadel.v1.ErrorDetail",
            "id": "QUERY-AG4gs",
            "message": "An internal error occurred"
        }
    ]
}

Call to /v2/users

Request body :
{
  "query": {
    "offset": "0",
    "limit": 100,
    "asc": true
  },
  "sortingColumn": "USER_FIELD_NAME_EMAIL",
  "queries": [
    {
      "inUserIdsQuery": {
        "userIds": [
          "337531633278126348"
        ]
      }
    }
  ]
}

500 Response :
{
    "code": 13,
    "message": "An internal error occurred (QUERY-AG4gs)",
    "details": [
        {
            "@type": "type.googleapis.com/zitadel.v1.ErrorDetail",
            "id": "QUERY-AG4gs",
            "message": "An internal error occurred"
        }
    ]
}

Call to /v2/users

Request body :
{
  "query": {
    "offset": "0",
    "limit": 100,
    "asc": true
  },
  "sortingColumn": "USER_FIELD_NAME_EMAIL",
  "queries": [
    {
      "inUserIdsQuery": {
        "userIds": [
          "337531633278126348"
        ]
      }
    }
  ]
}

500 Response :
{
    "code": 13,
    "message": "An internal error occurred (QUERY-AG4gs)",
    "details": [
        {
            "@type": "type.googleapis.com/zitadel.v1.ErrorDetail",
            "id": "QUERY-AG4gs",
            "message": "An internal error occurred"
        }
    ]
}

Call to /v2/users

Request body :
{
  "query": {
    "offset": "0",
    "limit": 100,
    "asc": true
  },
  "sortingColumn": "USER_FIELD_NAME_EMAIL",
  "queries": [
    {
      "inUserIdsQuery": {
        "userIds": [
          "337531633278126348"
        ]
      }
    }
  ]
}

500 Response :
{
    "code": 13,
    "message": "An internal error occurred (QUERY-AG4gs)",
    "details": [
        {
            "@type": "type.googleapis.com/zitadel.v1.ErrorDetail",
            "id": "QUERY-AG4gs",
            "message": "An internal error occurred"
        }
    ]
}

Previously, this query returned a 200 with the list of users found. Doc about this endpoint: https://zitadel.com/docs/apis/resources/user_service_v2/user-service-list-users

On the Zitadel instance pod, here is the log that I can see:

2025-12-02T11:23:03.821813793Z time="2025-12-02T11:23:03Z" level=info msg=activity caller="/home/runner/work/zitadel/zitadel/internal/activity/activity.go:105" domain="**********" grpcStatus=13 httpStatus=500 instance=************* isSystemUser=false method=/zitadel.user.v2.UserService/ListUsers org=************ path=/v2/users requestMethod=POST trigger=resourceAPI user=***************

2025-12-02T11:23:03.821813793Z time="2025-12-02T11:23:03Z" level=info msg=activity caller="/home/runner/work/zitadel/zitadel/internal/activity/activity.go:105" domain="**********" grpcStatus=13 httpStatus=500 instance=************* isSystemUser=false method=/zitadel.user.v2.UserService/ListUsers org=************ path=/v2/users requestMethod=POST trigger=resourceAPI user=***************

2025-12-02T11:23:03.821813793Z time="2025-12-02T11:23:03Z" level=info msg=activity caller="/home/runner/work/zitadel/zitadel/internal/activity/activity.go:105" domain="**********" grpcStatus=13 httpStatus=500 instance=************* isSystemUser=false method=/zitadel.user.v2.UserService/ListUsers org=************ path=/v2/users requestMethod=POST trigger=resourceAPI user=***************

2025-12-02T11:23:03.821813793Z time="2025-12-02T11:23:03Z" level=info msg=activity caller="/home/runner/work/zitadel/zitadel/internal/activity/activity.go:105" domain="**********" grpcStatus=13 httpStatus=500 instance=************* isSystemUser=false method=/zitadel.user.v2.UserService/ListUsers org=************ path=/v2/users requestMethod=POST trigger=resourceAPI user=***************

Has anyone else experienced this kind of problem after migrating? Thank you all!

Ask Inkeep•12/2/25, 11:47 AM

Hi @myouf, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.

Ask Inkeep•12/2/25, 11:48 AM

Answer

I wasn't able to find a direct answer, here are some relevant sources:

[Bug]: v3.3.2 to v4 Migration Errors (1) : This GitHub issue documents similar 500 errors after upgrading to v4, where multiple API operations broke including viewing user details and assigning roles. The issue was traced to SQL syntax errors in queries involving the projections.user_auth_methods5projections.user_auth_methods5 table.
V2 Users API not working questions-help-bugsV2 Users API not working : This Discord thread discusses issues with the V2 Users API endpoint /v2/users/new/v2/users/new returning unexpected results, though the specific error differs from yours.

Since your issue involves 500 errors after migration to v4.2.0, I'd suggest clicking the "Ask for help" button to tag a team member who can review your specific database logs and query structure.

Ask Inkeep•12/2/25, 11:48 AM

To learn more, see the sources I considered:

[1] [Bug]: v3.3.2 to v4 Migration Errors
questions-help-bugsV2 Users API not working

Ask Inkeep•12/2/25, 11:48 AM

Feel free to tag @Ask Inkeep with additional questions.

AAsk Inkeep To learn more, see the sources I considered: [[1] [Bug]: v3.3.2 to v4 Migrati...

Ask InkeepAPP•12/2/25, 11:52 AM

Got it. Tagging @Rajat for additional help.

myoufOP•12/2/25, 12:15 PM

Linked issue: https://github.com/zitadel/zitadel/issues/11119