Parameter header is not displayed in the rendered doc

We are using custom headers in our API endpoints but they are not displayed in the rendered docs.
Are we doing something wrong or is this a bug in the app?

Here is an example:

"paths": {
    "/product/api/v1/app/{appId}/userroles": {
      "get": {
        "tags": [
          "Role API for Authorization and UI"
        ],
        "summary": "Get user ",
        "description": "Retrieve data required to build token (roles, claims, userUuid, tenantUuid) based on user external Id, tenant tenantAlias and appId. ...",
        "operationId": "GetUserRoles",
        "parameters": [
          {
            "in": "path",
            "name": "appId",
            "schema": {
              "type": "string",
              "example": "appAlias"
            },
            "required": true,
            "description": "The Id of the Deployed App (appId)"
          },
          {
            "in": "header",
            "name": "X-Navify-Tenant",
            "schema": {
              "type": "string",
              "example": "roche-dis"
            },
            "required": true,
            "description": "tenantAlias from \"X-Navify-Tenant\" HTTP Header"
          },
          {
            "in": "header",
            "name": "Authorization",
            "schema": {
              "type": "string"
            },
            "required": true,
            "description": "valid IdP (Okta) token with user external Id from Authorization HTTP header"
          }
        ],
        "responses": {

Rendered doc

Hi @dawid.rutkowski, is this an OpenAPIv3 specification? The headers should display in the request section, next to the other parameters.

Hi Ross,
Yes you are right this is an OAS3 specification, but unfortunately the header is not displayed in the Requests Parameters section. Wondering what we are doing wrong?