Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Please include the root cause in the exception message

Open
#83 1 comment 0 reactions 1 assignee View on GitHub

@mridang is already working on this.

Since Mar 4, 2026.

Assessment

This issue has not been assessed yet.

Description

Please include the root cause in the exception message in com.zitadel.ApiException class.
Currently, com.zitadel.ApiException.getMessage() returns a concatenation of "Error " and status code; the error returned is "Error 400", which is the HTTP status code for a bad client request.

For example, if I provide an invalid organisation name criterion for a search request that exceeds 200 characters, the root cause can be found in the response body, which contains the following content for the above example:
{"code": "invalid_argument", "message": "invalid ListOrganizationsRequest.Queries[0]: embedded message failed validation | caused by: invalid SearchQuery.NameQuery: embedded message failed validation | caused by: invalid OrganizationNameQuery.Name: value length must be between 1 and 200 runes, inclusive"}.

A more user-friendly error message from com.zitadel.ApiException.getMessage(): "Error 400: invalid OrganizationNameQuery.Name: value length must be between 1 and 200 runes, inclusive"

Dominant language
Java
Stars
9
Forks
4
Avg merge
1h 40m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from zitadel/client-java

All issues in zitadel/client-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.