[BUG] Running (some) queries does nothing

[n9]

What is the bug?
Clicking Run on some queries does nothing. The error is only visible in the browser console:

Detected an unhandled Promise rejection.
TypeError: Cannot read properties of undefined (reading 'values')

queryWorkbenchDashboards.chunk.1.js:1 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'values')
    at queryWorkbenchDashbo…chunk.1.js:1:166079
    at Array.map (<anonymous>)
    at getQueryResultsForTable (queryWorkbenchDashbo…chunk.1.js:1:165473)
    at queryWorkbenchDashbo…chunk.1.js:1:169268

More information can be found in the browser network:

{
    "data": {
        "ok": true,
        "resp": "{\"error\":{\"reason\":\"There was internal problem at backend\",\"details\":\"WILDCARD fieldName types are currently not supported.\",\"type\":\"IllegalArgumentException\"},\"status\":500}"
    }
}

or when querying by alias:

{
    "data": {
        "ok": true,
        "resp": "{\"error\":{\"reason\":\"There was internal problem at backend\",\"details\":\"Index type [some_index_alias] does not exist\",\"type\":\"IllegalArgumentException\"},\"status\":500}"
    }
}

How can one reproduce the bug?
Steps to reproduce the behavior:

1. Have an index with a wildcard field.
2. Write a SQL query that uses this field.
3. Click Run.
4. Nothing happens.
5. Check browser console and see error.

What is the expected behavior?
Errors should be visible to user.

What is your host/environment?

• Google Chrome: 130.0.6723.92
• OpenSearch+Dashboards+Plugins: 2.17.1 (also reproduced on 2.16.0)

Do you have any additional context?

• When wildcard fields are expected to be supported?
• Index aliases are not supported?